Source properties and the unexpanded source code
Is it possible to access unexpanded source code information from the expanded source code in psyntax.scm? When I look at the source properties given to the build-xxx procedures there is only line number, column number, and filename. - Tommi Höynälänmaa
Re: [ANN] guile-commonmark 0.1 (A markdown parser)
On Sun, Jul 24, 2016 at 10:33 PM, Erik Edrosa wrote: > > As a bonus for haunt users, here is an example using guile-commonmark as > a reader to generate a blog written in markdown. > > (use-modules (haunt asset) > (haunt builder blog) > (haunt builder atom) > (haunt reader) > (haunt site) > (haunt post) > (commonmark)) > > (define commonmark-reader > (make-reader (make-file-extension-matcher "md") >(lambda (file) > (call-with-input-file file >(lambda (port) > (values (read-metadata-headers port) > (commonmark->sxml port))) > > (site #:title "Built with Guile" > #:domain "example.com" > #:default-metadata > '((author . "Eva Luator") > (email . "e...@example.com")) > #:readers (list commonmark-reader) > #:builders (list (blog) >(atom-feed) >(atom-feeds-by-tag))) > > Now just save the above as haunt.scm and put your markdown blog posts in > the posts directory with a .md extension and run `haunt build`. Here is > an example blog post: > > title: Hello World! > date: 2016-07-24 10:00 > tags: guile, commonmark, scheme > --- > > A CommonMark Document > === > Here is some *scheme* `code` > ```scheme > (display "Hello, World!") > ``` > > 1. A list > 2. Another item in a list > > Read more about [CommonMark](http://commonmark.org/) > > > Please note the header on top portion of the post which allows you to > add metadata to your blog posts for haunt. This is just wonderful! Thank you! If you have the time/motivation, I would love to see a patch to Haunt itself that adds guile-commonmark as an optional dependency. There's prior art for this because guile-reader is also optional, so it would mostly be a copy/paste job in configure.ac and Makefile.am to conditionally include the markdown reader module in the list of source modules. - Dave
Re: [ANN] guile-commonmark 0.1 (A markdown parser)
On 07/25/2016 09:44 AM, Thompson, David wrote: > On Sun, Jul 24, 2016 at 10:33 PM, Erik Edrosa wrote: >> >> As a bonus for haunt users, here is an example using guile-commonmark as >> a reader to generate a blog written in markdown. >> >> (use-modules (haunt asset) >> (haunt builder blog) >> (haunt builder atom) >> (haunt reader) >> (haunt site) >> (haunt post) >> (commonmark)) >> >> (define commonmark-reader >> (make-reader (make-file-extension-matcher "md") >>(lambda (file) >> (call-with-input-file file >>(lambda (port) >> (values (read-metadata-headers port) >> (commonmark->sxml port))) >> >> (site #:title "Built with Guile" >> #:domain "example.com" >> #:default-metadata >> '((author . "Eva Luator") >> (email . "e...@example.com")) >> #:readers (list commonmark-reader) >> #:builders (list (blog) >>(atom-feed) >>(atom-feeds-by-tag))) >> >> Now just save the above as haunt.scm and put your markdown blog posts in >> the posts directory with a .md extension and run `haunt build`. Here is >> an example blog post: >> >> title: Hello World! >> date: 2016-07-24 10:00 >> tags: guile, commonmark, scheme >> --- >> >> A CommonMark Document >> === >> Here is some *scheme* `code` >> ```scheme >> (display "Hello, World!") >> ``` >> >> 1. A list >> 2. Another item in a list >> >> Read more about [CommonMark](http://commonmark.org/) >> >> >> Please note the header on top portion of the post which allows you to >> add metadata to your blog posts for haunt. > > This is just wonderful! Thank you! > > If you have the time/motivation, I would love to see a patch to Haunt > itself that adds guile-commonmark as an optional dependency. There's > prior art for this because guile-reader is also optional, so it would > mostly be a copy/paste job in configure.ac and Makefile.am to > conditionally include the markdown reader module in the list of source > modules. > > - Dave > Definitely, I have been playing around with haunt and managed to switch my current blog to use haunt and guile-commonmark. I have a couple of ideas to add to haunt, so I will hopefully be sending you some patches soon. Thanks, Erik
FOSDEM 2016 was awesome! Let's do FOSDEM 2017
FOSDEM 2017 call for proposals has started: https://fosdem.org/2017/news/2016-07-20-call-for-participation/ We need help with writing the proposal (we can build on last years this time), we need help on selecting talks and we need help creating the schedule. Finally, if we get a slot, we need help to organise the day. Who wants to be part of this exciting day? Pj. On Tue, Feb 02, 2016 at 11:35:45AM -0800, Christopher Allan Webber wrote: > Alex Sassmannshausen writes: > > > Hello, > > > > Ludovic Courtès writes: > > > >> Hi there! > >> > >> I just came back from FOSDEM where we had an awesome Guile devroom with > >> nice people and great talks! > > > > I really want to echo Ludo's sentiments. I had a great time in our dev > > room and it was really nice to put faces to the names I see popping up > > in IRC and on the mailing list. I really hope we'll be able to do this > > again next year! > > An extra echo from me. > > >> The room of 80 seats was full pretty much all the time, and I think we > >> were all excited to see so many people stop by the devroom. Many shared > >> the impression that we were at an important moment of Guile’s history. > >> The transition with the Lua track that followed was also insightful and > >> a pleasant experience. > > I was optimistic about this being a big moment in Guile's history, but > after this FOSDEM, my enthusiasm and excitement has doubled, maybe > tripled! I can't wait to see what's happening in the year ahead! > > >> I would like to send a big Thank You to Pjotr Prins who took the > >> initiative and organized all this masterfully, from applying for the > >> devroom, to contacting potential speakers (dozens and dozens of > >> messages!), to getting up early on Saturday to make sure everything > >> would be fine in the devroom… Pjotr, you did an awesome job! > >> > >> Thanks to Paul van der Walt who also woke up early to help out with > >> video in the devroom, and obviously, thanks to all the speakers and > >> attendees! > > > > +1 for sure. Thank you very much for the commitment in time and energy! > > > > Alex > > Yes, thank you! :) --
