Bug#384697: [cl-debian] Bug#384697: cl-launch: need to modify script variables without touching the script

Xavier Maillard zedek at gnu.org
Sun Aug 27 22:41:49 UTC 2006


   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





More information about the Cl-debian mailing list