From: Vadim K. <va...@gm...> - 2007-04-13 16:52:53
|
I have the problem with .clisprc.lisp I placed my config parameters there (this is mostly load paths) and they are perfectly loaded when I go into interactive shell (clisp or even maxima) and they are loaded when I invoke clisp to run something from command line (clisp -x "something") The file .clisprc.lisp is entirely ignored when I run clisp against some file, e.g. search paths are not found. This makes .clisprc.lisp file much useless, IMO. "clisp --help" mentions about "-i file" but this means I must invoke every time my files with clisp -i [full-path-to-init-file-because-no-search-path-yet] my-file.lisp Can you please advise what I am missing? Do I misunderstand the idea of "clisprc" file? Thanks in advance, Vadim. |
From: Sam S. <sd...@gn...> - 2007-04-13 18:08:53
|
Vadim Konovalov wrote: > I have the problem with .clisprc.lisp > > I placed my config parameters there (this is mostly load paths) and they > are perfectly loaded when I go into interactive shell (clisp or even > maxima) and they are loaded when I invoke clisp to run something from > command line (clisp -x "something") > > The file .clisprc.lisp is entirely ignored when I run clisp against some > file, e.g. search paths are not found. this is documented behavior: http://clisp.cons.org/impnotes/clisp.html#opt-exec-file "No RC file will be executed." See also http://clisp.cons.org/impnotes/quickstart.html#script-exec > "clisp --help" mentions about "-i file" but this means I must invoke > every time my files with > clisp -i [full-path-to-init-file-because-no-search-path-yet] my-file.lisp > > Can you please advise what I am missing? > Do I misunderstand the idea of "clisprc" file? The idea of "clisp foo" is that it is used in scripts. (IIUC, bash scripts do not load ~/.bashrc either). A script should be a more-or-less standalone (self-contained) program that is usable by many people (this is the philosophy behind the Unix notion of a "script", not necessarily the way you want to use them), so they should not rely on personal files to work correctly (unless the files are relevant to the specific script as opposed to the interpreter running it). Thus the behavior you observe is intended, documented, and (IMHO) reasonable. Scripts should load all the files they rely upon explicitly. In your specific case - if indeed all your RC file does is search path setting - I would recommend dumping an image. Sam. |
From: Vadim K. <va...@gm...> - 2007-04-13 18:30:23
|
Sam Steingold wrote: > Vadim Konovalov wrote: >> >> Do I misunderstand the idea of "clisprc" file? > > The idea of "clisp foo" is that it is used in scripts. > (IIUC, bash scripts do not load ~/.bashrc either). Very reasonable argument, BTW. Thanks a lot for the comprehensive explanation! Vadim. |
From: Sam S. <sd...@gn...> - 2007-04-15 14:41:26
|
> * Vadim Konovalov <inqere@tznvy.pbz> [2007-04-13 22:20:28 +0400]: > > Thanks a lot for the comprehensive explanation! you are welcome. thanks for your patience and persistence - I just noticed that a couple of your messages on the subject were blocked by spamassassin. -- Sam Steingold (http://sds.podval.org/) on Fedora Core release 6 (Zod) http://dhimmi.com http://truepeace.org http://memri.org http://palestinefacts.org http://ffii.org http://iris.org.il http://camera.org Growing Old is Inevitable; Growing Up is Optional. |