freenode/#lisp - IRC Chatlog
Search
23:09:16
Harag
|3b|: if you want to see simple docker for lisp with plenty on notes on what and why, I did these https://gitlab.com/Harag/simple-sbcl-swank-docker and https://gitlab.com/Harag/sbcl-gcloud-run-workaround
0:30:04
|3b|
ok, possibly figured out the docker stuff enough to send a pr https://github.com/icfpcontest2020/dockerfiles/pull/44 :)
0:31:35
|3b|
let me know if anyone sees anything obviously wrong, or suggestions for other C/CL libs worth including by default (went ahead and added some common ones to reduce build time, but people can overwrite parts of the ql dir with one in their submission for full control)
3:19:12
Oladon
I find myself needing to write a new combination Markdown (probably Commonmark?) + BBCode parser. What's the best approach, architecture/organization-wise, to ensure maximum utility for others while still attaining my aim of a combination parser?
4:32:53
gjulio__
Hey is anyone willing to share a snippet of a .gitattributes file for handling control-m line endings in a *.lisp file? I've been trying a million tactics and I can't seem to resolve the problem.
5:03:48
gjulio__
i solved it. added *.lisp text eol=crlf to .gitattributes. then added (add-hook 'before-save-hook 'delete-trailing-whitespace) to .emacs and then created new files, moved my lisp file to the new file, added the new file to my git repo, and now it's working. it seems like the *.lisp text eol=crlf stuff isn't retroactive. maybe i'm wrong?
5:11:03
gjulio__
not sure. i did edit parts of the file on a different computer that was windows, maybe it's from that?
5:39:14
fe[nl]ix
gjulio__: convert all CRLF line endings to LF and configure your Windows editors to use LF as well
5:40:16
gjulio__
thanks. i'm usually using linux, but i'll keep that in mind if i need to switch back.