freenode/lisp - IRC Chatlog
Search
9:30:28
antoszka
fukamachi seems to be very proficient at getting code out, but he doesn't seem to document much nor maintain the code
9:32:28
fiddlerwoaroof
The wookie web server also has a pretty good web framework, if you use it directly
9:35:01
sirkmatija_
hey about ningle, how do you serve static files? do you just put them into /www directory like with hunchentoot?
9:37:08
fiddlerwoaroof
sirkmatija_: https://github.com/fiddlerwoaroof/whitespace/blob/master/demo.lisp#L406
9:37:26
fiddlerwoaroof
That project is horrible in several ways, it was my very first biggish lisp project
9:42:40
sirkmatija_
I am at the stage where all my projects are either horrible biggish or horrible smallish projects
9:43:15
fiddlerwoaroof
Yeah, project architecture is surprisingly difficult, even at a fairly small scale
12:12:03
fiddlerwoaroof
Normal climacs does run and I've heard of people that use it, but I don't know how feature-complete it is
12:28:10
parjanya
I’m mostly curious about the GUI... is there anything I can look to see how it works?
14:11:23
beach
(First) Climacs is already a bit better than Emacs, but not enough for people to want to switch.
14:28:21
beach
There is a lot of code factoring in there. It depends on McCLIM and a CLIM library called ESA (for Emacs-Style Application).
14:29:30
beach
And it is not written the way I would write it today. There is a lot of :USE going on, so it is hard to figure out where each symbol comes from, at least by just looking at the code.
14:31:12
beach
So the code in this repository: https://github.com/robert-strandh/Climacs does not work and does not reflect what you get in Quicklisp.
14:33:05
beach
And in https://github.com/robert-strandh/Climacs it is still first Climacs, except a failed attempt to clean it up.
14:33:59
beach
This repository: https://github.com/robert-strandh/Second-Climacs contains a very embryonic version of Second Climacs. It can't easily be installed and executed yet.
14:38:00
beach
An X11 resource is a 32-bit number, but it has a few bits guaranteed to be 0 so that it can be encoded as a Lisp fixnum.
14:40:45
beach
Now, (first) Climacs depends on McCLIM, and currently the CLX backend is the only one truly working for McCLIM, but there is work going on for a Windows backend, and also for a framebuffer backend that could be used with other display servers.
14:43:41
beach
You are in for some work. But we will help you out if you have questions. For stuff like that, you may have better luck in the #clim channel.
14:46:07
beach
The CLX backend for McCLIM can currently work in two different ways. The old way is that each CLIM sheet is mapped to an X11 windows. The new way is that only a top-level window is created, and McCLIM is managing its own nested sheets.
14:49:01
beach
It's the new way, because it is closer to what other display servers would offer, so the code that lets McCLIM control nested sheets needs to work well in order to enable us to created other backends.
14:52:20
beach
The code for CLX is currently maintained by sharplispers: https://github.com/sharplispers/clx
14:53:19
beach
... and this is the current repository for McCLIM: https://github.com/robert-strandh/McCLIM
14:54:56
beach
jackdaniel, who is currently maintaining McCLIM, has done a great job factoring the code, fixing bugs, merging improvements from others, and also fixing CLX problems when they were encountered.
15:20:11
varjag
just the other day i loaded som textbook examples from late 1980s into sbcl, and they worked without modifications
15:28:57
varjag
http://trove.nla.gov.au/work/18000379?q&sort=holdings+desc&_=1487950116513&versionId=39949380
17:51:08
drmeister
I'm making progress running Cando/Clasp in a docker container. But swank is closing the connection again and in slime I get this message:
17:51:19
drmeister
Error running 'timer `slime-process-available-input': (error "Selecting deleted buffer")
18:17:06
fortitude
does it seem like a bad idea to generate gensyms at runtime to use as task/thread IDs?
18:17:22
fortitude
it's not actually interning anything, but I don't think *GENSYM-COUNTER* is thread-safe
18:51:24
pjb
fortitude: just use (incf *next-thread-id*) Why would you need to allocate a new symbol?
18:54:31
fortitude
I assume for readability; I wrote this code quite some time ago, and can't recall exactly what I was thinking
18:55:03
fortitude
it's questionable whether I even need a task ID, since you could always just return the task object itself unless you were serializing (which I'm not)
19:17:00
pjb
fortitude: it's usually easier to remember and reference small numbers or strings, than object identities.
19:44:04
fortitude
is there a common convention for including/excluding multiple items with #+ and #-?
20:06:34
|3b|
ACTION notes that most keyword arguments aren't on *features* so you can just do #+:a 1 to get rid of :a and 1
20:26:55
burtons
(var ...) declerations are being rendered as var(..) function calls; this doesn't happen on LW.
20:31:34
drmeister
Has anyone used cl-jupyter recently and would have a few minutes to answer a few questions about it?
20:55:35
fortitude
burtons: on my sbcl it does the right thing; did you maybe forget to use a package specifier for VAR?
20:56:18
fortitude
burtons: e.g. (ps:ps (ps:var foo)) ;=> "var foo;", but (ps:ps (var foo)) ;=> "var(foo);"