freenode/#lisp - IRC Chatlog
Search
6:14:59
phoe
before I connect to the slime, I mount my Lisp projects directory using sshfs on the same location, so /home/phoe/Projects/Lisp/ refers to the same directory with the same contents both on the remote machine and the local one.
6:15:28
phoe
this way I avoid problems with translating names from local to remote ones, because they are the same.
10:55:28
myrkraverk
This is related to linedit; I already have a fork of it under my own (github) name; but I want to pull in changes from another fork
11:00:40
myrkraverk
Ok, so I need to first checkout my copy, *then* pull in changes from the other repository? And what happens if I want to make a pull request for the "other repository" ?
11:36:30
myrkraverk
That seems to have worked; but now I have problems getting my local changes applied correctly.
11:38:16
myrkraverk
Long story short, I hacked the original linedit not to ask to quit when I did ctrl+d to exit.
11:39:10
myrkraverk
Now I get "Invalid initialization argument:" and I believe I'll have to apply some more hacks to a class hierarchy I don't fully understand yet.
12:50:38
jackdaniel
well, I do, that was a joke. linedit works fine-ish on sbcl and rather bad on ccl. it doesn't work at all on ecl
13:02:48
Bike
Usually you'd do (defvar *a* 1), and then later in some function or whatnot, have (+ *a* 2).
13:10:52
jackdaniel
wrapping defvar in other expressions is something unusual, and unusual is not something much appreciated when others read your code
13:13:47
light2yellow
but yeah, anyway, thank you for pointing this out. you can't know if I am aware
13:20:59
alandipert
i wrote a solution to a puzzle, thanks in advance for giving it a look and sharing any thoughts you might have on how it could be improved https://gist.github.com/alandipert/5cf98cba9b9709976a423e598097dac0
13:38:05
light2yellow
> The set of special operator names is fixed in Common Lisp; no way is provided for the user to define a special operator <- from http://www.lispworks.com/documentation/HyperSpec/Body/03_ababa.htm . so it means that I can overload, say, +, but cannot overload these? if so, why?
13:40:20
Bike
what that says is that you can't define new special operators. it doesn't say anything about redefining the existing ones
13:40:26
dlowe
due to the nature of the lisp reader, you can make it so that (+ 1 2) refers to your own +, but cl:+ will always be available and immutable
13:41:04
dlowe
also, a "special operator" in lisp perhaps means something different than what it might mean in other languages
13:41:37
dlowe
more exactly, a form with a special operator doesn't follow the evaluation rules for either macros or functions
14:58:05
phoe
making user-implementable special operators would require that the users now have access to implementation internals and details and can essentially change their implementation at will.
14:58:42
phoe
you can think of special operators as a special kind of macros that you are unable to expand because their expansion and therefore internals are hidden from the user.
15:15:29
jeosol
when you run on SBCL on terminal (i.e.., sbcl --dynamic-space-size xxx), and your application writes lots of output to terminal, can this make it freeze or it is due to something else. FYI, my program typically can run for several days
15:23:18
shrdlu68
jeosol: Writing a lot of output to stdout/stderr is not a necessary/sufficient condition for a program to freeze.
15:24:17
jeosol
shrdlu68: thanks for that. I checked two cases I was running on a local box. one froze, the other didn't.
15:24:45
jeosol
So I just checked. So I can rule that out. Those outputs help me know things are going ok. Thx
15:43:05
pelle
hi, i'm trying to install Quicklisp in SBCL, but it gives me this error: Don't know how to REQUIRE SB-BSD-SOCKETS.
15:45:13
phoe
to me, it seems that you got a SBCL that was built without --fancy, and therefore without BSD socket support.
15:46:47
pelle
Well.. ok, another problem. In Clisp, Quicklisp *does* install, but McClim fails with this error (but maybe that's for the #clim channel): SYSTEM::%FIND-PACKAGE: There is no package with name "ASDF-USER"
15:46:52
phoe
pelle: please do. Building a distro-wide SBCL without contribs sounds like a big mistake.
15:48:25
pelle
@phoe: i had some problems installing debian/ubuntu/... but alpine linux happened to work. weird laptop. but alpine linux uses musl instead of glibc
15:48:50
jeosol
I am running on xterm. Not sure what they other one freeze, might be better logging to some where else, a file and check the file
17:23:51
Xach
pelle: i think it's because clisp does not have asdf so it uses an old one from quicklisp.
17:25:49
pelle
Xach: yes, found out now: Clisp has an old ASDF. It's working fine in ECL though. I got some help on the #clim channel.