Kundry_Wag has quit [Remote host closed the connection]
Kundry_Wag has joined #lisp
Kundry_Wag has quit [Ping timeout: 256 seconds]
fisxoj has quit [Quit: fisxoj]
eli_oat has joined #lisp
eli_oat has quit [Client Quit]
mange has joined #lisp
eli_oat has joined #lisp
warweasle has joined #lisp
Kundry_Wag has joined #lisp
Kundry_Wag has quit [Read error: Connection reset by peer]
terpri has joined #lisp
comborico1611 has quit [Read error: Connection reset by peer]
Kundry_Wag has joined #lisp
Arcaelyx has joined #lisp
Arcaelyx has quit [Client Quit]
warweasle has quit [Quit: Leaving]
pierpa has quit [Quit: Page closed]
quazimodo has quit [Ping timeout: 256 seconds]
smurfrobot has quit [Ping timeout: 268 seconds]
karlosz has joined #lisp
<karlosz>
anybody get slime working on clisp?
<karlosz>
it seems to want a newer asdf version
<karlosz>
(require "asdf") doesnt even work
<akkad>
did you download a newer asdf?
<karlosz>
ah, i got it working the moment i asked
EvW has quit [Ping timeout: 276 seconds]
<karlosz>
i just needed to load uiop beforehand
Kaisyu has joined #lisp
Kundry_Wag has quit [Remote host closed the connection]
Kundry_Wag has joined #lisp
<karlosz>
okay, now quicklisp doesn't work on clisp :(
<karlosz>
something about QL-CLISP not existing
<akkad>
any reason for chosing clisp over sbcl?
<Beepy>
^
<karlosz>
well, i'm going to work on clisp, first of all
Kundry_Wag has quit [Ping timeout: 240 seconds]
<akkad>
then perhaps some assembly might be required
rmrenner has joined #lisp
<karlosz>
nope
<akkad>
so it all works?
<Bike>
i think clisp ships a really old asdf
<Bike>
i remember people coming here asking about it
<theemacsshibe[m]>
clisp is just really old
<Beepy>
Its website says 2010 was the last update
<karlosz>
well, it looks like this particular issue was fixed in the latest commit to quicklisp
<karlosz>
clisp master was updated 2 weeks ago
<karlosz>
except a quicklisp release hasnt been made yet
charh has quit [Quit: zZzZZzz]
eli_oat has quit [Quit: Leaving.]
pierpal has joined #lisp
pierpal has quit [Client Quit]
<Beepy>
karlosz, where are you seeing that it was updated?
<karlosz>
their version control
pierpal has joined #lisp
damke_ has joined #lisp
damke has quit [Ping timeout: 268 seconds]
<clintm>
Is clisp the one that gets updated by loading new code into a previous revs image? I remember reading about a CL that did that as opposed to building a new image like sbcl.
<Zhivago>
You can build an image from a system built from an imace in sbcl.
<Zhivago>
I wouldn't recommend it these days. Image building is pretty much something that was useful until dynamic linkage became available.
<Plazma>
oh Zhivago you hang out in here too eh?
<theemacsshibe[m]>
image making is nice tbh, i use it to distribute lisp programs to non-lisp users
d4ryus1 has joined #lisp
<Plazma>
while not the same, smalltalk also uses images (that are pretty easy to build/strip down) which is a cool concept I think still, even if it's a bit dated
<theemacsshibe[m]>
ehh, it's like having a compiled binary from C IMO
<theemacsshibe[m]>
it's possible to mess (especially with -g) with but not as good as having sources
Ober has joined #lisp
d4ryus has quit [Ping timeout: 260 seconds]
<Plazma>
in a sense it reminds me also of the .app binaries mac uses
<Plazma>
mostly self contained
<theemacsshibe[m]>
fair enough
<Plazma>
well partially, guess it depends
kolb has quit [Read error: Connection reset by peer]
ioa has quit [Read error: Connection reset by peer]
ioa has joined #lisp
damke has joined #lisp
mrottenkolber has joined #lisp
mrottenkolber is now known as Guest83051
damke_ has quit [Ping timeout: 268 seconds]
fikka has quit [Ping timeout: 260 seconds]
zooey has quit [Read error: Connection reset by peer]
kushal has quit [Write error: Connection reset by peer]
kushal has joined #lisp
zooey has joined #lisp
<karlosz>
clintm: clisp doesn't
<karlosz>
pretty much all the other common lisp in common lisps are though
<karlosz>
like CCL, CMUCL...
<karlosz>
sbcl is actually the exceotion
<karlosz>
its whole existence was ttying to move away from the CMUCL style build to the reproducible build we all know and love
<clintm>
ah, right, I must have been thinking of cmucl. thank you, karlosz
fikka has joined #lisp
rmrenner has quit [Ping timeout: 264 seconds]
quazimodo has joined #lisp
eli_oat has joined #lisp
fikka has quit [Ping timeout: 250 seconds]
fikka has joined #lisp
<Ober>
how far is Clasp from being usable as a primary implementation?
Arcaelyx has joined #lisp
fikka has quit [Ping timeout: 256 seconds]
<Beepy>
that's probably something to direct at drmeister
arescorpio has joined #lisp
<Bike>
depends on what you want ot do, i guess
<akkad>
"lisp stuff" haha
fikka has joined #lisp
fikka has quit [Ping timeout: 260 seconds]
<Ober>
will use QL to figure it out
eli_oat has quit [Quit: Leaving.]
LiamH has quit [Quit: Leaving.]
Pixel_Outlaw has quit [Remote host closed the connection]
rmrenner has joined #lisp
fikka has joined #lisp
fikka has quit [Ping timeout: 248 seconds]
quazimodo has quit [Ping timeout: 260 seconds]
<loke>
Ober: I don't think QL qorks with Clasp.
<Bike>
sure it does
pierpal has quit [Ping timeout: 260 seconds]
<loke>
Bike: Oh it does? I tried it a few moenths ago, and back then Drmeister said it was planned but not working yet.
<Bike>
yeah, pretty sure it's fine
<Bike>
asdf works and network works
server001 has joined #lisp
server001_ has joined #lisp
<Ober>
it dies doing the install here
<Bike>
building clasp?
<Ober>
no, on the quicklisp-quickstart:install step
<Ober>
process ends, and with it any logs
<Bike>
it might not know about clasp's initfile, i guess
dddddd has quit [Remote host closed the connection]
<Bike>
guess i'll take a look tomorrow
<Bike>
i've never had any problems
server001_ has quit [Client Quit]
<Ober>
trying setup.lisp with an existing copy. using drmeisters docker image
sz0 has joined #lisp
fikka has joined #lisp
<Ober>
cool. that works
pierpal has joined #lisp
terpri has quit [Ping timeout: 240 seconds]
fikka has quit [Ping timeout: 260 seconds]
pierpal has quit [Quit: Poof]
pierpal has joined #lisp
fikka has joined #lisp
rmrenner has quit [Remote host closed the connection]
fisxoj has joined #lisp
fikka has quit [Ping timeout: 268 seconds]
pierpal has quit [Remote host closed the connection]
nika has joined #lisp
fisxoj has quit [Quit: fisxoj]
smurfrobot has joined #lisp
fikka has joined #lisp
damke_ has joined #lisp
damke has quit [Ping timeout: 268 seconds]
fikka has quit [Ping timeout: 240 seconds]
fikka has joined #lisp
Oladon has joined #lisp
fikka has quit [Ping timeout: 240 seconds]
smurfrobot has quit [Remote host closed the connection]
schoppenhauer has quit [Ping timeout: 250 seconds]
smurfrobot has joined #lisp
slyrus2 has joined #lisp
schoppenhauer has joined #lisp
fikka has joined #lisp
smurfrobot has quit [Remote host closed the connection]
smurfrobot has joined #lisp
fikka has quit [Ping timeout: 240 seconds]
makomo has joined #lisp
fikka has joined #lisp
smurfrobot has quit [Remote host closed the connection]
smurfrobot has joined #lisp
fikka has quit [Ping timeout: 260 seconds]
fikka has joined #lisp
<aeth>
Does anyone else use a macro as the way to access things to avoid potentially dozens of exports in a package? What I've been doing is a with-foo-accessors that places the accessor symbols in the package specified at the definition of that macro and also can add a prefix (for the case of structs with conc-name not set to nil).
<aeth>
I find that this greatly simplifies things because then I only need to export the with-foo-accessors macro and/or a macro that indirectly uses that macro.
Beepy has quit [Ping timeout: 265 seconds]
<aeth>
e.g. (with-foo-accessors ((foo foo)) foobar ...) would macroexpand to (with-accessors ((foo the-package-containing-foobar::foobar-foo)) foobar ...) in the most complicated case (where it's a struct with prefixed accessors)
fikka has quit [Ping timeout: 246 seconds]
makomo has quit [Ping timeout: 268 seconds]
<on_ion>
aeth: neat =)
<pillton>
aeth: Yes, but not to avoid the number of symbols that are exported.
<aeth>
destructuring-lambda is just a lambda that does a destructuring bind on its one argument. It's surprisingly common. In fact, I just now noticed the pattern in define-accessor-macro
arescorpio has quit [Quit: Leaving.]
fikka has quit [Ping timeout: 265 seconds]
fikka has joined #lisp
raynold has quit [Quit: Connection closed for inactivity]
Bike has quit [Quit: Lost terminal]
iqubic has joined #lisp
fikka has quit [Ping timeout: 256 seconds]
smurfrobot has quit [Remote host closed the connection]
smurfrobot has joined #lisp
<loke>
aeth: What's with the INTERN calls in the macro?
fikka has joined #lisp
karlosz has quit [Quit: karlosz]
<aeth>
loke: Otherwise the macro will produce something whose API is (zombie-raptor/util/util::foo)
<aeth>
(well, something along those lines)
fikka has quit [Ping timeout: 276 seconds]
<loke>
aeth: Can't you just use &environment ?
shka_ has joined #lisp
terpri has joined #lisp
Kevslinger has quit [Quit: Connection closed for inactivity]
smurfrobot has quit [Remote host closed the connection]
oleo has quit [Quit: Leaving]
paul0 has joined #lisp
smurfrobot has joined #lisp
mflem has joined #lisp
<aeth>
How?
fikka has joined #lisp
asarch has quit [Quit: Leaving]
<loke>
aeth: instead of your reader macro dance, just use (intern "FOO" env)
fikka has quit [Ping timeout: 246 seconds]
<aeth>
loke: I use #.(symbol-name ...) pretty much everywhere instead of hardcoding the symbol as a string of upper case characters
doanyway has quit []
earl-ducaine has quit [Read error: Connection reset by peer]
<aeth>
I know it's essentially pointless, but at least to me it feels better to not hardcode the assumption about the reader that will almost certainly be valid. Perhaps this could be turned into something more concise?
flamebeard has joined #lisp
daniel-s has joined #lisp
earl-ducaine has joined #lisp
<aeth>
But... I suppose I should be using &environment env instead of assuming intern without that argument would work correctly
rumbler31 has joined #lisp
fikka has joined #lisp
Karl_Dscc has joined #lisp
rumbler31 has quit [Ping timeout: 256 seconds]
fikka has quit [Ping timeout: 256 seconds]
jameser has joined #lisp
jameser has quit [Remote host closed the connection]
fikka has joined #lisp
jameser has joined #lisp
vlatkoB has joined #lisp
jameser has quit [Ping timeout: 250 seconds]
fikka has quit [Ping timeout: 260 seconds]
damke has joined #lisp
fikka has joined #lisp
damke_ has quit [Ping timeout: 268 seconds]
pierpal has joined #lisp
Satou has joined #lisp
Karl_Dscc has quit [Remote host closed the connection]
beach has joined #lisp
<beach>
Good morning everyone!
eSVGDelux has joined #lisp
<iqubic>
Morning Beach.
<clintm>
Good morning, Beach!
eSVGDelux has quit [Client Quit]
<theemacsshibe[m]>
hi beach
eSVG has quit [Ping timeout: 255 seconds]
yeticry has joined #lisp
<loke>
Yes?
<loke>
Oops
heisig has joined #lisp
scymtym has quit [Ping timeout: 265 seconds]
hajovonta has joined #lisp
smurfrobot has quit [Remote host closed the connection]
Josh_2 has quit [Quit: ERC (IRC client for Emacs 25.3.1)]
RebelCoderRU has joined #lisp
<RebelCoderRU>
Hi. Can anyone please help with installing/running lisp on Debian ? I have installed it on my Py and I need it to run a server wit the following command:
<RebelCoderRU>
(load "start")
angavrilov has quit [Remote host closed the connection]
<RebelCoderRU>
But I get an error: pi@raspberrypi:~/gits/api $ (load "start")
<RebelCoderRU>
-bash: load: command not found
<RebelCoderRU>
Any help would be much appropriated
<pjb>
No, it cannot. Because ccl can only be compiled by ccl, it cannot be included in debian distributions.
fikka has joined #lisp
<RebelCoderRU>
I have the ARM tar unzipped...
<pjb>
Then you have sbcl, clisp and ecl that should be able to run on Raspberry Pi. Perhaps one of them might be in the distribution. But I would download the sources and compile it myself anyways…
<pjb>
RebelCoderRU: then, you would have to run the CL implementation first, and give it expressions to evaluate once it's launched. You cannot do that at the bash REPL, you have to do it at the CL REPL!
<pjb>
RebelCoderRU: it's the same principle as with Python, ruby (irb), perl, or even bash.
<RebelCoderRU>
OK. Just need to find the way to install CLL now
<pjb>
ccl = Clozure CL, not CLL.
<RebelCoderRU>
Sorry, CCL , yes
<antoszka>
RebelCoderRU: Whatever you do, you need to get your Lisp REPL first (the "prompt") rather than typing Lisp code directly in the shell :)
<pjb>
RebelCoderRU: you may also have a look at http://cliki.net/Getting+Started for installation beyond the CL implementation. Ie. you may want to install quicklisp (the CL librarian), and a good editor for lisp such as emacs with slime and paredit.
<antoszka>
RebelCoderRU: You might also want to join #clnoobs if you require a bit more handholding :)
<RebelCoderRU>
A-ha !
<RebelCoderRU>
Doing the quicklisp now....
<RebelCoderRU>
Thanks
<antoszka>
Cool.
<antoszka>
RebelCoderRU: What is the project you're trying to get running?
<RebelCoderRU>
I think I can do it without joining noobs...