freenode/#lisp - IRC Chatlog
Search
5:29:37
drmeister
::notify shiho Pull the latest clasp 'dev' and start building it again. I had introduced a problem in the previous version that only showed up when building quicklisp. The new 'dev' fixes it.
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