freenode/lisp - IRC Chatlog
Search
16:15:44
makomo
contrapunctus: not me, but there's also this project/product which seems interesting https://wukix.com/mocl
16:25:09
jackdaniel
eql5-android worked fine for me when I was playing with it, there are quite a few examples in the source tree
16:44:22
jackdaniel
dto's games worked with sdl on the other hand. there is ecl's performance bottleneck with clos dispatch we plan to address *after* the upcoming release
19:29:13
skeuomorf
jackdaniel: Do you have any idea whether I can have a post as an HTML file that will be rendered as-is? Using coleslaw I mean
19:33:02
skeuomorf
jackdaniel: hmm https://github.com/kingcons/coleslaw/blob/master/src/content.lisp#L114
20:43:38
oleo
papachan: put the asdf source into /common-lisp/source build there and then try (require :asdf) (asdf:load-system :asdf)
20:52:19
oleo
had to find them all via find . type d -name sbcl-1.4.7-x64 -exec rm -rf {} \; and delete
1:38:32
skeuomorf
PuercoPop: It would be cool if the links to CSS files, images, ...etc are relative to the root instead of being tied directly to the domain
2:02:57
skeuomorf
PuercoPop: e.g. https://hackage.haskell.org/package/hakyll-3.2.7.1/docs/Hakyll-Web-Urls-Relativize.html
2:03:53
PuercoPop
skeuomorf: The themes are hardcoding the ${config.domain} as the prefix. You could set the domain in the .coleslawrc as the root URL of your blog
2:05:40
skeuomorf
PuercoPop: put another way, given index, I want to be able to navigate to everywhere else from it without being tied to the domain name, so that all the URLs are relative to index
2:07:24
jason_m
Hello, I recently discovered snooze (https://github.com/joaotavora/snooze). This is a small issue, but the defroute indentation does not work for me as shown in the readme. Can I change how that works? (emacs / slime)
2:07:48
PuercoPop
For the posts content you can use the relative URL, or are you asking for something else?
2:09:37
PuercoPop
skeuomorf: I'm guessing the the easiest way is to just copy the theme to a new dir a modify the templates directly. I know there is PAGE-URL but I'm not seeing a way to achieve what you want easily. Then again I haven't read the codebase in quite a while. I still have to incorporate the docs on using Roswell
2:11:09
skeuomorf
PuercoPop: say I have a .coleslawrc with domain name as "http://example.com", and I have 2 posts, post1.md and post2.md, when I open index.html locally and try to navigate to post1, i get redirected to "example.com/post1" instead of "/root/post1"
2:11:58
skeuomorf
PuercoPop: I have a custom theme already, but this behavior is the same across my theme and hyde
2:16:41
PuercoPop
COMPUTE-URL is a function unfortunately. Maybe if we change it to a generic function you could specialize the method according the 'content-type' you wish?
2:18:25
skeuomorf
PuercoPop: Sorry, I don't think I understand what this has to do with content types
2:20:13
PuercoPop
skeuomorf: If I'm understanding you correctly you want to change the URL of Posts. Or do you want to change the URL of Post in a particular page?
2:22:02
PuercoPop
So URLs belong to the content itself and they are determined by COMPUTE-URL :after initializing the instance of the content (tag/post/etc). So you'd have to modify that if you want to change the URL of a content-type, like POSTS.
2:23:58
skeuomorf
PuercoPop: https://hackage.haskell.org/package/hakyll-3.2.7.1/docs/Hakyll-Web-Urls-Relativize.html
2:29:29
PuercoPop
skeuomorf: Ah ok. Yeah no, that is not something that Coleslaw can easily do. URLs are property of the content itself not something that is dynamically computed in relation to the 'current' content
2:36:41
PuercoPop
skeuomorf: I don't really have a good answer short of come up with a 'URL protocol' similar to the 'Document Protocol' and replace the URL reader of content with it? The post templates are receive the currently post as an argument so in theory you should be able to to use that as the current 'context/base'
2:39:20
skeuomorf
PuercoPop: The gh-pages plugin doesn't seem to work, neither when using (gh-pages :cname t) nor (gh-pages :cname "http://example.com")
2:45:12
PuercoPop
skeuomorf: Weird the last one should work. In fact Im not sure how the otherwise clause should be reachable because t should catch everything. Including nil
2:46:52
PuercoPop
skeuomorf: Yeah, and it was written before the 'new gh-pages'. Let me try to run use it locally
2:55:39
PuercoPop
skeuomorf: it does, after I remove the truename call in the initial (let ((blog (truename ..)))
2:59:26
skeuomorf
PuercoPop: Awesome, trying to find out where quicklisp installs packages so that I can edit my Coleslaw and not have to wait for a release :)
3:02:23
skeuomorf
PuercoPop: Nice on the `where-is`, it's actually `where-is-system`, still new to Common Lisp
3:07:26
skeuomorf
PuercoPop: Do I need to do anything after editing the file other than reloading coleslaw?
3:08:27
PuercoPop
skeuomorf: no, you don't even need to reload coleslaw, just C-c C-c over the function to compile it again
3:17:48
PuercoPop
skeuomorf: yeah. I haven't seen them in quite a while. You could @ them at twitter or shoot them an email
3:23:11
skeuomorf
PuercoPop: Found these though, where you commented https://github.com/kingcons/coleslaw/issues/84 and https://github.com/kingcons/coleslaw/issues/142
3:27:52
skeuomorf
I noticed that a user had sent a patch but you objected to it for some reason, do you have an idea of how we can fix it properly?
3:30:17
PuercoPop
skeuomorf: do you have the link handy? I only remember rejecting the djula plugin but only because I could come up with a way to handle both the render from the 'outside to the inside' of closure-templates and djul'as from the 'inside to the outside'
3:30:58
skeuomorf
PuercoPop: oh, I meant your comment here https://github.com/kingcons/coleslaw/issues/142#issuecomment-335061002
3:33:00
PuercoPop
I meant that the sitemap is conceptually an index and not content (and the link at the end should be https://github.com/kingcons/coleslaw/commit/78f1fc9fa05c4134e8fe9cd2069350da8ebf6458)
3:37:23
skeuomorf
PuercoPop: when I generate a blog to a deploy-dir, it overwrites the .git repo, is there a way currently to preserve this?