freenode/#lisp - IRC Chatlog
Search
19:42:02
on_ion
phoe: er, already mentioned those earlier. intent of comparison to squeak smalltalk ChangeSets, those are portable across implementations and machines. they are essentially source code diffs.
20:02:29
pjb
Most often you cannot apply such patch, even on the same implementation and machine, when you try to apply them on a different version.
20:21:38
jmercouris
I'm reading this article here: http://joaotavora.github.io/sly/#A-SLY-tour-for-SLIME-users about SLY
20:21:49
jmercouris
and I'm wondering, any SLY users in here? can you tell me why you prefer it to Slime?
20:25:38
jmercouris
I don't see anything that can't also be done in slime, but maybe I'm just missing some things
20:27:44
Bike
this intro is starting with a bunch of stuff slime doesn't have, so maybe i'm misunderstanding you
20:29:24
Bike
i doubt sly is going for some kind of amazing transcendental experience, just better than slime
20:44:12
Xach
I remember I didn't want to try slime because i liked ILISP. But actually using it showed me how wrong I was. Even though at a high level they do the same things.
20:49:41
Xach
The slime video helped a ton in persuading me to try it. Reading static pages and screenshots, and using your imagination, is not always persuasive
21:02:34
dim
the cost of changing one's habit is very high, and slime is pretty good at what it does already
21:19:22
attila_lendvai
slime has most of the cool stuff stuffed away in contribs, e.g. the fuzzy completion
0:42:40
mfiano
The benefit of Sly is builtin mrepl, stickers, everything being a button to inspect, amoung many improvements and bug fixes.
0:44:11
mfiano
as of a few days ago, even builtin company completion with zero configuration that is much snappier than the old sly-company, or slime-company
0:45:01
mfiano
I switched from SLIME to Sly about 3 years ago and I'm still happy with that choice whenever I am reminded by using SLIME
2:00:13
kuwze
Xach: does this still work for you? http://lispblog.xach.com/post/112939066338/using-paredit-within-screen
5:38:16
asarch
I did: (ql:quickload "clim-examples") in "This is SBCL 1.3.14.debian, an implementation of ANSI Common Lisp." and everything is fine, however when I do: (clim-demo:demodemo) I get: https://pastebin.com/0adz1s7D
6:39:14
jackdaniel
since quicklisp distribution seems to be the same, you probably have another mcclim copy somewhere in local-projects or common-lisp directory
6:39:42
jackdaniel
notice difference in instructions: ";; try (CLIM-DEMO:DEMODEMO)" vs ";; try (CLIM-DEMO::DEMODEMO)"
6:41:57
asarch
I didn't see this: ./.cache/common-lisp/sbcl-1.3.14.debian-linux-x64/usr/share/common-lisp/source/mcclim