Unnamed repository; edit this file to name it for gitweb.
git clone https://logand.com/git/picolisp.git/
Log | Files | Refs | README | LICENSE

commit 0619b3ea6f2f00991b560ab09a1b5ea1e132921b
parent 1ce1e5ee11337a75e665bcbd141849ed5a4376df
Author: Alexander Burger <abu@software-lab.de>
Date:   Thu,  5 May 2011 12:11:19 +0200

Global vs. local invocation
Mdoc/ref.html | 30+++++++++++++++++++++++++++---
1 file changed, 27 insertions(+), 3 deletions(-)

diff --git a/doc/ref.html b/doc/ref.html @@ -52,6 +52,7 @@ href="faq.html">Frequently Asked Questions (FAQ)</a>. </ul> <li><a href="#penv">Programming Environment</a> <ul> + <li><a href="#inst">Installation</a> <li><a href="#invoc">Invocation</a> <li><a href="#io">Input/Output</a> <ul> @@ -488,6 +489,29 @@ and environment are described. <p><hr> +<h3><a name="inst">Installation</a></h3> + +<p>PicoLisp supports two installation strategies: Local and Global. + +<p>Normally, if you didn't build PicoLisp yourself but installed it with your +operating system's package manager, you will have a global installation. This +allows system-wide access to the executable and library/documentation files. + +<p>To get a local installation, you can directly download the PicoLisp tarball, +and follow the instructions in the INSTALL file. + +<p>A local installation will not interfere in any way with the world outside its +directory. There is no need to touch any system locations, and you don't have to +be root to install it. Many different versions - or local modifications - of +PicoLisp can co-exist on a single machine. + +<p>Note that you are still free to have local installations along with a global +installation, and invoke them explicitly as desired. + +<p>Most examples in the following apply to a global installation. + + +<p><hr> <h3><a name="invoc">Invocation</a></h3> <p>When PicoLisp is invoked from the command line, an arbitrary number of @@ -516,7 +540,7 @@ reserved for application programs. immediately by calling <code><a href="refB.html#bye">bye</a></code>: <pre><code> -$ bin/picolisp -bye +$ picolisp -bye $ </code></pre> @@ -525,7 +549,7 @@ href="refL.html#load">load</a></code>) will also exit when <code>Ctrl-D</code> is entered: <pre><code> -$ bin/picolisp +$ picolisp : $ # Typed Ctrl-D </code></pre> @@ -534,7 +558,7 @@ loaded. The most commonly used things are in "lib.l" and in a bunch of other files, which are in turn loaded by "ext.l". Thus, a typical call would be: <pre><code> -$ bin/picolisp lib.l ext.l +$ picolisp lib.l ext.l </code></pre> <p>The recommended way, however, is to call the "pil" shell script, which