i'd imagine that, for most development setup and for newbies, getting output setup to *inferior-lisp* or the remote slime's terminal is not what you want. any problems if i change this to t?
Marco Baringer mb@bese.it writes:
i'd imagine that, for most development setup and for newbies, getting output setup to *inferior-lisp* or the remote slime's terminal is not what you want. any problems if i change this to t?
p.s. - i'm assuming that it works correctly on all the various lisp systems, correct me if i'm wrong.
On 9/26/06, Marco Baringer mb@bese.it wrote:
Marco Baringer mb@bese.it writes:
i'd imagine that, for most development setup and for newbies, getting output setup to *inferior-lisp* or the remote slime's terminal is not what you want. any problems if i change this to t?
p.s. - i'm assuming that it works correctly on all the various lisp systems, correct me if i'm wrong.
I agree that T would be the more preferable default.
Unfortunately this stopped working for me, I would guess something like a month ago. I just checked, and this feature of the current cvs slime does not work on: - OS X on an Intel MacBook - very recent cvs Gnu Emacs - SBCL 0.9.16
If memory serves, it also stopped working on one of my Linux boxes (Gentoo, older SBCL) at the same time it broke on the laptop, but I haven't checked that recently. I can do if it's of any help.
Cheers, Bill.
"William Bland" doctorbill.news@gmail.com writes:
I agree that T would be the more preferable default.
I'm fine with that too.
Unfortunately this stopped working for me, I would guess something like a month ago. I just checked, and this feature of the current cvs slime does not work on:
- OS X on an Intel MacBook
- very recent cvs Gnu Emacs
- SBCL 0.9.16
The time when this happened was probably a while back (late spring or early summer unless memory fails), when SBCL changed the way special variables work with threads: threads used to inherit the bindings from their parents, which i no longer the case -- all threads use the global bindings unless the variable has been bound in the thread.
And before you ask, no *default-special-bindings* and equivalents don't exist yet, but will "soon".
Cheers,
-- Nikodemus Schemer: "Buddha is small, clean, and serious." Lispnik: "Buddha is big, has hairy armpits, and laughs."
nikodemus@random-state.net wrote:
The time when this happened was probably a while back (late spring or early summer unless memory fails), when SBCL changed the way special variables work with threads:
That was in SBCL 0.9.6 (October 2005).
-
Juho Snellman -
Marco Baringer -
Nikodemus Siivola -
William Bland