libera/#commonlisp - IRC Chatlog
Search
8:24:30
flip214
[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~[6~
8:25:09
hayley
Hopefully I'll get into the mood to work on Netfarm again, but I'm not expecting that right now.
8:26:50
hayley
I have holiday time, and then a semester of part-time study, so I should be able to help out though.
8:35:37
hayley
(That said, w.r.t Netfarm, for most of 2021 I felt like everyone wanted the opposite of what I was working on. Recently I had some success sharing around some articles I wrote, but those articles have nothing to do with Netfarm.)
8:54:14
hayley
Still lots of fun to be had in any case. A friend is slowly getting closer to specifying and implementing enough of a message-sending object-oriented object-capability language, and I've been tasked with working out how to make a metacircular implementation for it. But that is not Common Lisp related (and that's the point :)
12:36:47
nij-
Is there anyway to let Climacs to read elisp and be augmented by packages written in elisp? The idea is that to attract more people temporarily, and gradually replace the packages by common lisp.
12:40:12
lisp123
nij-: I was thinking something similar, but different - write an elisp emulator in CL and port Emacs
12:42:01
nij-
E.g. some elisp package has effects on emacs buffer. So at least we need to coerce emacs buffer into climacs buffer?
12:44:06
lisp123
I was arguing with some people on r/Emacs but they noted that most of the more advanced elisp packages are already using a CL compatability layer
12:44:30
lisp123
So I wouldn't be suprised if there is an influx of package developers in the future
12:44:31
random-nick
nij-: I don't think that's very feasible, you'd have to emulate a lot of emacs internals for elisp packages to work
12:47:22
lisp123
For example, I am working a general framework for GUIs in SwiftUI (Apple), and if you create the APIs on both sides, you can have Lisp programmers write in CLIM and then have it displayed in Swift for example
12:48:22
nij-
Yeah lets just focus on the end effect. It's a temporary solution, just to let people switch to climacs without pain.
12:48:48
lisp123
The #clim guys are doing much more - canvas backends among other things. Then dbotton is doing CLOG
12:49:53
beach
nij-: (first) Climacs is not good enough. And Second Climacs is mainly meant to be excellent for editing Common Lisp code.
12:53:23
beach
Emacs packages rely not only on the Emacs Lisp programming language, but a lot on the architecture of Emacs, so you would have to emulate that entire architecture, which would mean you no longer have (first) Climacs or Second Climacs, but Emacs rewritten in Common Lisp.
12:54:50
beach
I think it is a much better strategy to make Second Climacs irresistibly good for Common Lisp programming, and then count on the users to perhaps rewrite their favorite Emacs packages for Second Climacs over time.