IRC channel logs

2016-08-18.log

back to list of logs

<daviid>night!
<daviid>any particular reason why in guile's source tree, the guile.m4 file is in meta and not in m4 subdir? in my own projects, I put it (a modified version that also defines GUILE_GLOBAL_SITE_DIR and GUILE_SITE_CCACHE_DIR) in m4 subdir
<daviid>just curious really
<amz3`>héllo :)
<OrangeShark>morning
<dsmith-work>Morning Greetings, Guilers
***Guest84127 is now known as PaulE
***PaulE is now known as Guest76395
***Guest76395 is now known as PaulCam
<catern>Hi, does GSRC actually work to build the most recent guile release?
<catern>I get a missing bdw-gc error
<amz3>GSRC?
<mark_weaver>I'm not sure if anyone here uses GSRC, dunno.
<mark_weaver>I guess you should report the problem to them
<amz3>at last I ordered reasoned schemer and sicp!
<amz3>and joined the fsfe :)
<OrangeShark>amz3: I enjoyed SICP
<amz3>soon enough I will understand all of minikanren without asking ijp all the time
<OrangeShark>I need to read the reasoned schemer though
<amz3>OrangeShark: I read the code of minikanren but I discovered recently that the version of the code I was reading was incomplete
<amz3>OrangeShark: by the way what's you pet project ?
<OrangeShark>amz3: my most recent project was a CommonMark parser
<amz3>ah yes
<amz3>I saw it on the mailling list
<amz3>I did not read the code tho
<amz3>OrangeShark: you do other projects?
<OrangeShark>CommonMark is a specified version of Markdown
<amz3>OrangeShark: yes, I read about that, I don't like the CommonMark syntax honestly
<amz3>I prefer to use # chars to mark headings
<amz3>the CommonMark way of underlining the titles, reminds of restructured text
<OrangeShark>you can use # chars to mark headings as well
<amz3>OrangeShark: really... oO
<amz3>did not know that
<OrangeShark>it supports both
<OrangeShark>I think underline heading is in original markdown as well
<amz3>hmm, that's good news actually
<OrangeShark> https://daringfireball.net/projects/markdown/syntax#header
<OrangeShark>yup, they were
<OrangeShark>I have just a bunch of other random projects written in other languages, but I really gained a liking to scheme
<amz3>me too, most of my projects are python or javascript
<amz3>I even have a project with 45 stars... woohoo!
<davexunit>OrangeShark: guile-commonmark is great :)
<OrangeShark>davexunit: thanks, I need to work on improving it though to support the current spec though.
<amz3>what is it missing?
<OrangeShark>the biggest thing is it currently expands tabs into spaces, which the spec used to have, but they removed it
<OrangeShark>tabs are pretty important for code blocks :P
<amz3>do you support the ``` aka. github syntax too?
<OrangeShark>yup
<amz3>cool
<OrangeShark>```language-name
<amz3>it means, I can drop it in my project doc and work with it
<davexunit>oh cool
<OrangeShark>so you can use a JS syntax highlighter
<davexunit>now people can contribute lexers to guile-syntax-highlight and have their haunt blogs do syntax highlighting of their markdown posts ;)
<OrangeShark>yup :)
<OrangeShark>I was thinking of adding some lexers to guile-syntax-highlight
<davexunit>OrangeShark: I need to revisit my pelican->haunt blog migration project. I think I'll use markdown for the posts now :)
<amz3>wait, you can highlight CommonMark code with guile-syntax-highlight?
<davexunit>amz3: no, but you could highlight the parsed source blocks
<davexunit>since the document can include an identifier for the language
<OrangeShark>amz3: it not integrated, but you can parse the sxml
<OrangeShark>to find the code blocks to highlight
<amz3>ah ok
<davexunit>I think once guile-syntax-highlight is actually released I will add it as an optional dependency for haunt
<amz3>does guile-syntax-highlight support rainbow delimiters?
<davexunit>so that syntax highlighting will "just work" for supported languages
<davexunit>amz3: not currently, but it could be done
<amz3>ok thx
<OrangeShark>I was thinking of also adding options to the github fences too
<amz3>what is it?
<davexunit>when iterating the list of tokens you could keep track of the delimiter nesting level
<OrangeShark>```language-name various options
<davexunit>oh neat
<davexunit>didn't know about those
<OrangeShark>the spec says you only take the first word as the language
<davexunit>I think we can have a very nice blogging platform on our hands here :)
<OrangeShark>and you can do whatever you want with the rest
<davexunit>OrangeShark: do you have a blog deployed anywhere that uses haunt with guile-commonmark?
<davexunit>just curious to see it in practice, if there is an example :)
<OrangeShark>ya, I changed my personal website from my own static site generator to haunt
<davexunit>is the repo available?
<OrangeShark>ya
<davexunit>or a link to your site?
<davexunit>I'm a bit embarrassed that I wrote haunt and never finished converting my blog to use it
<OrangeShark> https://github.com/OrangeShark/blog
<davexunit>wonderful!
<amz3>nice!
<OrangeShark>haunt is pretty great, way better than my personal static site generator that I wrote in python lol
<davexunit>thanks :)
<davexunit>I'm happy to see that other people took interest in it
<OrangeShark>I was originally going to create my own static site generator in guile, but then you showed off yours and it looked really good. So I decided to go the route of writing a commonmark/markdown parser for it instead :P
<davexunit>it's much appreciated. what's a static site generator without markdown support?
<OrangeShark>yup, it the most popular format people use. I know people kept mentioning wanting markdown support for haunt ;P
<davexunit>I'm adding an example markdown post to the repo
<OrangeShark>awesome, I will send more patches to update the docs.
<OrangeShark>I also have some ideas for more builders to add to haunt
<davexunit>OrangeShark: ooh like what?
<OrangeShark>I was thinking for robot.txt and sitemap.txt
<davexunit>oh yeah that would be very useful
<amz3>sitemap.txt?
<amz3>txt?
<OrangeShark>it a file that can be used by search engines
<OrangeShark>the robot.txt can provide a url to it
<davexunit>OrangeShark: just made my first markdown post. works like a charm!
<OrangeShark>davexunit: nice :)
<OrangeShark>amz3: well by web crawlers
<amz3>it's sitemap.xml I think not txt
<OrangeShark>some support a simple txt format which is a list of urls
<amz3>ok
<davexunit>OrangeShark: I'll need to write a little function that can identify code blocks in the SXML and run them through the syntax highlighter. is parsing ```scheme as class="language-scheme" specified in the standard?
<davexunit>(lazy question, I know, I just don't feel like digging through the spec)
<OrangeShark>yup, you need to prepend language-
<davexunit>okay
<davexunit>that's an easy transformation to make
<davexunit>find the block, parse language, replace the body with the result of the syntax highlighter
<OrangeShark>yup, seems simple enough
<davexunit>I'll do that the next time I have some real free time.
<davexunit>ACTION is excited
<davexunit>I can definitely finish my blog conversion with this
<davexunit>I rue the day I chose to use restructuredtext instead of markdown when I made my blog...
<davexunit>but should be a lot less work to convert to markdown than to skribe
<amz3>from 50k urls I retrieve I can use only 914, most of them are now redirects :(
<amz3>I should check for redirects
<amz3>I will follow the white rabbit
<OrangeShark>amz3: are you going to crawl the pages which those urls go to?
<amz3>that's what I did
<amz3>but most of them are broken now
<amz3>they are actually not all redirects but 404s
<amz3>I calculated to dumping the whole hackernews at current speed would take 12 days
<amz3>I hope I made a mistake
<amz3>Maybe I will have a brillant idea after lunch!
<OrangeShark>wow, a lot of 404s? That is pretty bad
<mark_weaver>amz3: have you considered writing a parser for the archive.org JSON dump that avoids loading the whole thing into memory at once?
<mark_weaver>(I remember you mentioning such a dump, but that it was too big to load into memory, iirc)
<mark_weaver>JSON is pretty simple to write a parser for, shouldn't be much work.
<stis>evening guilers!
<stis>I think that I'm converging on a good representation for a generilized and feature ful set datastructure.
<stis>I tried to extend it to operations on map as well and incorporate the logic of simple assoc logic
<stis>as well as allow complements
<amz3>stis: is it about prolog?
<amz3>mark_weaver: yes
<stis>It's about scheme and prolog. I implement the datastructures and framwork in scheme
<stis>I use it in prolog with fancy operators etc
<stis>So it can be used in scheme, actually I have a repo for it with scheme only code
<stis>'set-o-mat'
<stis>This is old stuff. I realized that I was wrong about my earlier take.
<stis>SO I wrote a blog about it hoping to get more eues on this and spread the idea
<stis> http://c-lambda.se/set-mania.html
<stis>I'l have a few takes more on this and then I will modify the source code.
<stis>to include the proper feature
<stis>examples is on prolog unfourtunately, but easy to understand
<stis>I just wanted to express the math and examples in colors and choose the prolog colorizer basically
<stis>and also be used as documentation for the feature in prolog
<catonano>what are (ice-9 mvars) ? Does the manual talk about them anywhere ?
<ijp>anyone else getting secure connection issues from savannah from firefox?
<lfam>ijp: What kind of issues?
<lfam>ijp: I recently had this problem while using Debian Iceweasel / Firefox: http://savannah.gnu.org/support/?109089
<ijp>seems to be the same issue
<lfam>ijp: In the end, I backed up my ~/.mozilla directory and then hand-edited Savannah out of my '~/.mozilla/firefox/$my-profile/SiteSecurityServiceState.txt'
<lfam>But, be sure you understand the implications of that before you do it
<lfam>By editing that file, you are bypassing an important security feature of the browser
<lfam>It would be good if you chimed in on that bug report