libera/#commonlisp - IRC Chatlog
Search
16:40:35
Xach
Hmm, is there anything standard-ish (cltl2 included) to get the name of the function enclosing a macro or compiler-macro at macroexpansion time?
16:43:10
Bike
What do you mean by enclosing? Like, if a macro is being expanded, the name of the function whose body the macro form is in?
16:43:28
Krystof
don't think so. a cltl2-ish environment might have information about block names, but I think even allegro doesn't have a "list-all-blocks-in-this-environment" exported operator
16:52:36
Xach
Krystof: thanks. block names were my first thought but the env object I have is a bit more opaque to me than SBCL's
16:57:07
dieggsy
with slime/sly is there no way to make sure all output is shown in the repl buffer (as opposed to some going to the inferior lisp buffer) ?
16:58:52
scymtym
Xach: the log4cl library must have something like that but i doubt it is even remotely standard-ish
17:02:42
Xach
Allegro would be most useful to me in fact. Time to scrape around the env object a little more.
17:59:04
jackdaniel
(1+ most-positive-fixnum) ways for making repl unusable: (setf *print-right-margin* (1+ most-positive-fixnum))
18:24:33
pjb
jackdaniel: it's a non-negative integer, so (1+ most-positive-fixnum) is perfectly conforming.
20:07:07
Shinmera
the new update argument also allows posting four pictures, and very large gifs or videos.
3:28:11
dieggsy
or, is it possible to run a lisp function defined in the current environment in a separate process
3:30:16
dieggsy
we basically have some legacy build script written in bash and lisp, and i thought "why not just do this in only lisp", but then was like "oh wait because it compiles and loads a bunch of stuff", so I'm trying to... both integrate the code but also separate it from the current environment when it runs ? if that makes any sense at all
4:19:19
dieggsy
ludston: thanks, though that largely concerns launching external programs as a process, and I want to run some lisp as a process
4:19:44
ludston
If for whatever reason you need to sandbox some function in another process, you probably just spin up a new lisp instance with --load "(my lisp code here)"