From: Ivan Z. <mel...@me...> - 2013-09-28 21:14:17
|
Hi again :) What would be the best way to customize the Lisp site? Say, I want to change the values of some variables or run some commands every time clisp starts. clisprc.lisp is not sufficient because I want custom behavior for scripts as well (otherwise it would be). The notes say, edit config.lisp and recompile; is this the way to go? Should I just cp src/cfgunix.lisp src/config.lisp and add to the latter? |
From: Pascal J. B. <pj...@in...> - 2013-09-29 03:41:32
|
Ivan Zaigralin <mel...@me...> writes: > Hi again :) > > What would be the best way to customize the Lisp site? Say, I want > to change the values of some variables or run some commands every > time clisp starts. > > clisprc.lisp is not sufficient because I want custom behavior for > scripts as well (otherwise it would be). The notes say, edit config.lisp > and recompile; is this the way to go? Probably not. If the notes say that, it probably means you have to go into the closest wood, walk 1 mile north, 2 miles east, wait in the glade till full month, kill a goat, collect its blood, walk 1 mile west, 2 miles south, turn 3 times, drink the blood, and sing "woowhaawhoowhaa". Yes, I guess that's what it means. > Should I just > > cp src/cfgunix.lisp src/config.lisp > > and add to the latter? Have you tried it? -- __Pascal Bourguignon__ http://www.informatimago.com/ |
From: Pascal J. B. <pj...@in...> - 2013-09-29 03:49:22
|
"Pascal J. Bourguignon" <pj...@in...> writes: > Ivan Zaigralin <mel...@me...> writes: > >> Hi again :) >> >> What would be the best way to customize the Lisp site? Say, I want >> to change the values of some variables or run some commands every >> time clisp starts. >> >> clisprc.lisp is not sufficient because I want custom behavior for >> scripts as well (otherwise it would be). The notes say, edit config.lisp >> and recompile; is this the way to go? > > Probably not. If the notes say that, it probably means you have to go > into the closest wood, walk 1 mile north, 2 miles east, wait in the > glade till full month, kill a goat, collect its blood, walk 1 mile west, > 2 miles south, turn 3 times, drink the blood, and sing > "woowhaawhoowhaa". > > Yes, I guess that's what it means. > > >> Should I just >> >> cp src/cfgunix.lisp src/config.lisp >> >> and add to the latter? > > Have you tried it? That said, there's an alternative: you could save a customized image (eg. with a specific init-function) and have it loaded by the clisp driver. -- __Pascal Bourguignon__ http://www.informatimago.com/ |
From: Ivan Z. <mel...@me...> - 2013-09-30 23:09:04
|
On 09/28/2013 11:22 PM, Pascal J. Bourguignon wrote: > Ivan Zaigralin <mel...@me...> writes: > >> Hi again :) >> >> What would be the best way to customize the Lisp site? Say, I want >> to change the values of some variables or run some commands every >> time clisp starts. >> >> clisprc.lisp is not sufficient because I want custom behavior for >> scripts as well (otherwise it would be). The notes say, edit config.lisp >> and recompile; is this the way to go? > > Probably not. If the notes say that, it probably means you have to go > into the closest wood, walk 1 mile north, 2 miles east, wait in the > glade till full month, kill a goat, collect its blood, walk 1 mile west, > 2 miles south, turn 3 times, drink the blood, and sing > "woowhaawhoowhaa". > > Yes, I guess that's what it means. > > >> Should I just >> >> cp src/cfgunix.lisp src/config.lisp >> >> and add to the latter? > > Have you tried it? I have now. It doesn't seem to work. I am trying to (setf custom::*parse-namestring-ansi* t) if it makes any difference. Any idea why it doesn't work? |
From: Ivan Z. <mel...@me...> - 2013-09-30 23:16:25
|
I guess, I could also just run scripts with #!/usr/bin/clisp -i whatever but it bugs me that a file gets loaded (a pointless performance hit for a few setf instructions). On 09/30/2013 07:08 PM, Ivan Zaigralin wrote: > > > On 09/28/2013 11:22 PM, Pascal J. Bourguignon wrote: >> Ivan Zaigralin <mel...@me...> writes: >> >>> Hi again :) >>> >>> What would be the best way to customize the Lisp site? Say, I want >>> to change the values of some variables or run some commands every >>> time clisp starts. >>> >>> clisprc.lisp is not sufficient because I want custom behavior for >>> scripts as well (otherwise it would be). The notes say, edit config.lisp >>> and recompile; is this the way to go? >> >> Probably not. If the notes say that, it probably means you have to go >> into the closest wood, walk 1 mile north, 2 miles east, wait in the >> glade till full month, kill a goat, collect its blood, walk 1 mile west, >> 2 miles south, turn 3 times, drink the blood, and sing >> "woowhaawhoowhaa". >> >> Yes, I guess that's what it means. >> >> >>> Should I just >>> >>> cp src/cfgunix.lisp src/config.lisp >>> >>> and add to the latter? >> >> Have you tried it? > > I have now. It doesn't seem to work. I am trying to > > (setf custom::*parse-namestring-ansi* t) > > if it makes any difference. Any idea why it doesn't work? > > > > ------------------------------------------------------------------------------ > October Webinars: Code for Performance > Free Intel webinars can help you accelerate application performance. > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from > the latest Intel processors and coprocessors. See abstracts and register > > http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk > > > > _______________________________________________ > clisp-list mailing list > cli...@li... > https://lists.sourceforge.net/lists/listinfo/clisp-list > |
From: Pascal J. B. <pj...@in...> - 2013-10-02 20:07:28
|
Ivan Zaigralin <mel...@me...> writes: > On 09/28/2013 11:22 PM, Pascal J. Bourguignon wrote: >> Ivan Zaigralin <mel...@me...> writes: >> >>> Hi again :) >>> >>> What would be the best way to customize the Lisp site? Say, I want >>> to change the values of some variables or run some commands every >>> time clisp starts. >>> >>> clisprc.lisp is not sufficient because I want custom behavior for >>> scripts as well (otherwise it would be). The notes say, edit config.lisp >>> and recompile; is this the way to go? >> >> Probably not. If the notes say that, it probably means you have to go >> into the closest wood, walk 1 mile north, 2 miles east, wait in the >> glade till full month, kill a goat, collect its blood, walk 1 mile west, >> 2 miles south, turn 3 times, drink the blood, and sing >> "woowhaawhoowhaa". >> >> Yes, I guess that's what it means. >> >> >>> Should I just >>> >>> cp src/cfgunix.lisp src/config.lisp >>> >>> and add to the latter? >> >> Have you tried it? > > I have now. It doesn't seem to work. I am trying to > > (setf custom::*parse-namestring-ansi* t) > > if it makes any difference. Any idea why it doesn't work? Works perfectly: [pjb@kuiper :0.0 clisp-hg]$ ./configure --with-libsigsegv-prefix=${prefix} --prefix=/data/languages/clisp-pjb --hyperspec=http://localhost/local/lisp/www.lispworks.com/documentation/HyperSpec/ && echo ' (setf custom::*parse-namestring-ansi* t) (defparameter cl-user::*pjb* :configured) ' >> src/config.lisp && make -C src && make -C src install > > > executing ../src/configure --with-libsigsegv-prefix=/data/src/languages/clisp/clisp-hg/tools/x86_64-unknown-linux-gnu --prefix=/data/languages/clisp-pjb --hyperspec=http://localhost/local/lisp/www.lispworks.com/documentation/HyperSpec/ configure: loading cache config.cache … make: Leaving directory `/data/src/languages/clisp/clisp-hg/src' [pjb@kuiper :0.0 clisp-hg]$ /data/languages/clisp-pjb/bin/clisp -q -norc [1]> *pjb* :CONFIGURED [2]> custom::*parse-namestring-ansi* T [3]> (quit) [pjb@kuiper :0.0 clisp-hg]$ -- __Pascal Bourguignon__ http://www.informatimago.com/ |
From: Ivan Z. <mel...@me...> - 2013-10-02 21:45:46
|
I'll be damned. After I adapted your way and created a new file rather than copied cfgunix.lisp and added to the end, it worked! I wonder, is it because cfgunix.lisp starts with (in-package "EXT")? But how would that affect setting that variable? There is so much I don't understand about CL :) Anyways, thanks a bunch, this is exactly what I wanted. But now I am leaning towards simply wrapping the binary in, like, bash or something ;) On 10/02/2013 04:05 PM, Pascal J. Bourguignon wrote: > Ivan Zaigralin <mel...@me...> writes: > >> On 09/28/2013 11:22 PM, Pascal J. Bourguignon wrote: >>> Ivan Zaigralin <mel...@me...> writes: >>> >>>> Hi again :) >>>> >>>> What would be the best way to customize the Lisp site? Say, I want >>>> to change the values of some variables or run some commands every >>>> time clisp starts. >>>> >>>> clisprc.lisp is not sufficient because I want custom behavior for >>>> scripts as well (otherwise it would be). The notes say, edit config.lisp >>>> and recompile; is this the way to go? >>> >>> Probably not. If the notes say that, it probably means you have to go >>> into the closest wood, walk 1 mile north, 2 miles east, wait in the >>> glade till full month, kill a goat, collect its blood, walk 1 mile west, >>> 2 miles south, turn 3 times, drink the blood, and sing >>> "woowhaawhoowhaa". >>> >>> Yes, I guess that's what it means. >>> >>> >>>> Should I just >>>> >>>> cp src/cfgunix.lisp src/config.lisp >>>> >>>> and add to the latter? >>> >>> Have you tried it? >> >> I have now. It doesn't seem to work. I am trying to >> >> (setf custom::*parse-namestring-ansi* t) >> >> if it makes any difference. Any idea why it doesn't work? > > Works perfectly: > > [pjb@kuiper :0.0 clisp-hg]$ ./configure --with-libsigsegv-prefix=${prefix} --prefix=/data/languages/clisp-pjb --hyperspec=http://localhost/local/lisp/www.lispworks.com/documentation/HyperSpec/ && echo ' > (setf custom::*parse-namestring-ansi* t) > (defparameter cl-user::*pjb* :configured) > ' >> src/config.lisp && make -C src && make -C src install >>>> executing ../src/configure --with-libsigsegv-prefix=/data/src/languages/clisp/clisp-hg/tools/x86_64-unknown-linux-gnu --prefix=/data/languages/clisp-pjb --hyperspec=http://localhost/local/lisp/www.lispworks.com/documentation/HyperSpec/ > configure: loading cache config.cache > … > make: Leaving directory `/data/src/languages/clisp/clisp-hg/src' > [pjb@kuiper :0.0 clisp-hg]$ /data/languages/clisp-pjb/bin/clisp -q -norc > [1]> *pjb* > :CONFIGURED > [2]> custom::*parse-namestring-ansi* > T > [3]> (quit) > [pjb@kuiper :0.0 clisp-hg]$ > |
From: Pascal J. B. <pj...@in...> - 2013-10-02 22:01:09
|
Ivan Zaigralin <mel...@me...> writes: > I'll be damned. After I adapted your way and created a new file > rather than copied cfgunix.lisp and added to the end, it worked! > I wonder, is it because cfgunix.lisp starts with (in-package "EXT")? > But how would that affect setting that variable? There is so much I > don't understand about CL :) > > Anyways, thanks a bunch, this is exactly what I wanted. But now I am > leaning towards simply wrapping the binary in, like, bash or something ;) By the way, if you're interested in standard behavior, you can invoke clisp with -ansi: #!/usr/bin/clisp -q -ansi also equivalent to: (setf custom:*ansi* t) in ~/.clisprc.lisp -- __Pascal Bourguignon__ http://www.informatimago.com/ |