I'm not sure we either need or want a /etc/cl-launchrc or a
~/.cl-launchrc. After all, the user (or root) may already export the
variable $LISP to override things at runtime (or at dump time),
whatever the --lisp or $LISPS variable be, unless explicitly prevented
with a --wrap argument (or a resetting of $LISP), and I think that's
all we need.
I second this.
As for stumpwm, note that I prefer the more versatile --init argument:
'(stumpwm:stumpwm (cl-launch:getenv "DISPLAY"))'
to a hardcoded :0.
Oh nice enhancement ! I did not know I could do this. Thank you.
--
Xavier
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
