Re: Installation

[Alexander Burger]

Hello Henrique,

> Recently, I tried to build PicoLisp from source (master branch at github).
> I've followed the instructions at INSTALL, but GNU Make complains that it
> can't find "../bin/picolisp" (from "src" directory). Am I supposed to
> download an executable and insert it there in order to build PicoLisp? I
> hope that doesn't mean PicoLisp depends on itself.

PicoLisp does indeed depend on itself, but it comes with pre-built *.ll
files, so make should succeed out of the box.

Only if you modify *.l files, the *.ll files need to be rebuilt, and
this requires a running picolisp.

However, if you clone from a repo, the file timestamps may be destroyed,
and make possibly finds *.l files newer than the *.ll files.

The best is you fetch the TGZ with the rolling release

   https://software-lab.de/pil21.tgz

File meta data are preserved in tar files.


This is also described in

   https://software-lab.de/INSTALL

Good luck! :)

☺/ A!ex

-- 
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Re: Installation and update

[cilz]

Hi Mike, All,

Thanks for these tips. I was not aware of: pil @lib/test.l +

to check the installation.

Here, I'm using Manjaro Linux and Picolisp can be installed from the Aur 
repo with:


yay -S picolisp

however it installs version (18-9-1) which is not up to date!

Install from source works well however.

Take care,

Eric


Le 07/01/2020 à 20:06, Mike a écrit :

hi all,

I've wrote all information how I do install and update of PicoLisp over all my 
machines.
Page contains 3 variations how to bootstrap to pil64.
https://git.envs.net/mpech/tankf33der/src/branch/master/install-picolisp.md

Comments and updates are welcome

(mike)



--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Re: Installation and update

[Tomas Hlavaty]

On NixOS, picolisp has been available out of the box on 32 and 64 bit
intel and arm:

$ nix-shell -p picolisp

-- 
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Re: Installation and update

[Priyadarshan]

Thank you for that detailed guideline, very helpful to
understand more.

For now I am using PiCoLisp on Debian Unstable via WSL 1
(Windows 10), but I will need to use it on an illumos (omniOS)
server sooner or later.

Is this list a good place to ask for question about the very
nice code repository you have made available? Or perhaps other
ways?

Priyadarshan

Tuesday, January 7, 2020, 8:06:35 PM, you wrote:

> hi all,

> I've wrote all information how I do install and update of PicoLisp over all 
> my machines.
> Page contains 3 variations how to bootstrap to pil64.
> https://git.envs.net/mpech/tankf33der/src/branch/master/install-picolisp.md

> Comments and updates are welcome

> (mike)



-- 
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Re: Installation and update

[O.Hamann]

Hi Mike,

I like that, looks straight forward.

(after following it for the ubuntu track, one little suggestion: '*
ready to compile pil64' fits perfectly into the ascii view of the .md
file, but in the html view I overlooked it several times because it's
much less attracting attention)

I've never used CentOS so far, so it would be a real test if I could run
pil64 with that doc :-)   (I have to try it, but no promise).


As I'm more used to Ubuntu flavors of Linux,

here is one for an actually downloaded Ubuntu Desktop 19.10 -
bootstrapping via picolisp package only

(I wondered there was no need to install gcc or other utilities, but
okay ...)

Greetings, Olaf

--- snip ---

# you have fresh installed Ubuntu 19.10 x64 ('minimal' chosen in install
dialog)

## bootstrap via outdated pil64  package
```
cd ~
sudo apt install picolisp
pil -version -bye
19.7.5
pil @lib/test.l -bye +  # error without +
OK

```

* ready to compile pil64


## fetch and install latest picoLisp tarball

```
wget https://software-lab.de/picoLisp.tgz

tar zxvf picoLisp.tgz
(cd picoLisp/src64 ; make)


export PATH=$PATH:/home/user/picoLisp

```

## remove previously installed package

```
sudo apt purge picolisp

```

## test

```
pil -version -bye
20.1.3# should not show 19.7.5

pil @lib/test.l -bye +
OK

```

---snip


On 07.01.2020 20:06, Mike wrote:

hi all,

I've wrote all information how I do install and update of PicoLisp over all my 
machines.
Page contains 3 variations how to bootstrap to pil64.
https://git.envs.net/mpech/tankf33der/src/branch/master/install-picolispmd

Comments and updates are welcome

(mike)



--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Re: Installation / Load Paths

[Alexander Burger]

Hi Christopher, Andreas,

> > I could install all my supporting files in @lib/ in the picolisp 
> > installation directory.
> That is one way to do it. Alex usually does it this way afaik.

I would not store application-specific stuff under @lib/, but it is true that on
production servers I usually have the current working directory at @/ (for the
local installation. The global installation at /usr/bin/ etc. is left as it is).


> You could also create your own custom directory within the picolisp directory
> and then refer to it with "@myDirectory/my-lib.l".

Yes.


> The argument(s) to (load) don't have to start with "@".
> So you could also load from absolute paths, e.g.:
> -  (load "/home/user/programname/foo.l"))
> -  (load (pack *Prefix "/share/programname/foo.l"))
> 
> The current directory is not changed during executing of (load), so if the
> loaded files refer to additional files, those paths should also be absolute.

The same (*Prefix) would hold when all paths were relative.


> There are also:
> - (cd "/home/user/programname") -> change the current directory permanently
> - or (chdir) to change the directory just for some 'prgs, e.g. (chdir 
> "/home/user/programname") (load "foo.l"))
> 
> In my installations I always execute the program in it's own directory or
> switch to that directy with (cd), anD I load all includes from relative paths.

I second that. Usually you will have to keep in mind not only the 'load'ed
sources, but also data files like config stuff and the database and blob
directories, so I find changing the working (sic) directory the best way.

♪♫ Alex

-- 
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

RE: Installation / Load Paths

[andreas]

Hi Christopher

> I could install all my supporting files in @lib/ in the picolisp installation 
> directory.
That is one way to do it. Alex usually does it this way afaik.

You could also create your own custom directory within the picolisp directory 
and then refer to it with "@myDirectory/my-lib.l".

The argument(s) to (load) don't have to start with "@".
So you could also load from absolute paths, e.g.:
-  (load "/home/user/programname/foo.l"))
-  (load (pack *Prefix "/share/programname/foo.l"))

The current directory is not changed during executing of (load), so if the 
loaded files refer to additional files, those paths should also be absolute.
You can find out the current directory your program is executing in with (pwd) 
-> this is the start point for relative paths.

There are also:
- (cd "/home/user/programname") -> change the current directory permanently
- or (chdir) to change the directory just for some 'prgs, e.g. (chdir 
"/home/user/programname") (load "foo.l"))

In my installations I always execute the program in it's own directory or 
switch to that directy with (cd), and I load all includes from relative paths.

Best regards,
beneroth


- Original Message -
From: Christopher Howard [mailto:christopher.how...@qlfiles.net]
To: picolisp@software-lab.de
Sent: Sat, 02 Sep 2017 07:47:42 -0800
Subject: Installation / Load Paths

Hi, what is the customary way PicoLisp programmers deal with load path
issues when trying to install a completed program onto a Gnu/Linux
system? My program has two *.l files. What I wanted to do was:

- Put the *.l files in $(PREFIX)/share/programname/
- Have a bash or picolisp script in $(PREFIX)/bin that starts the
program in $(PREFIX)/share/programname.
- Preferably do all this without having to modify the callers CWD.

This creates some difficulties because one of the source files simply
does a (load "myothermodule.l"), which works great when running from
the source directory, but not when installed somewhere outside the CWD.
Do I need to change that to (load "@myothermodule.l) and modify the @
variable somehow during invocation? Or I guess I could install all my
supporting files in @lib/ in the picolisp installation directory.

Or is there some other "load-path" mechanism in picolisp I'm not
seeing...?

--
https://qlfiles.net
https://emailselfdefense.fsf.org/en/

Re: Installation issues

[Alexis]

On 2015-02-17T17:12:54+1100, Alexander Burger said: 

AB> as I mentioned in my previous mail, is Thorsten currently AB> 
offline.  He asked me to post this for him  
  A> "i'll try to find some time to: 

  A> * examine the diffs between the distribution version and the 
  A> GitHub version; 

 TJ> Why? Just use the newer version, i.e. the Github  TJ> 
 version. Nobody else but me did change anything recently. 

Then why isn't the GitHub version the one currently distributed 
with PicoLisp? The fact that it's not suggested to me there might 
be some issues around doing so. And why does the distribution 
version contain picolisp-wiki-mode.el, whereas the GitHub version 
doesn't?   (A separate issue is, why do users have to manually 
patch  paredit.el?  Has there been some issue with upstream not 
being  willing or able to modify paredit.el so that it can better 
support  PicoLisp?) 

  A> * add to the former any fixes and/or extra functionality  A> 
  found in the latter; 

 TJ> Again - why? Just replace the older version with the  TJ> 
 newer version ... 

See above. 

  A> * add in my code to present documentation for the symbol at 
  A> point; 

 TJ> and you mean an eldoc implementation for picolisp? 

No, although that's certainly a good idea. What my code does is 
(for Emacs > 24.3) to open the full reference documentation for a 
particular function in a new buffer via `shr`, or (for Emacs < 
24.4) in a Web browser. 

 TJ> patches are welcome, just fork me on github. 

... except you're currently offline, for a period of time not 
specified. As i've mentioned elsewhere in this thread, given my 
experiences of spending time coding and submitting PRs/issues, 
only to have the latter ignored even by people who are 
demonstrably still actively coding, i'm not much inclined to get 
involved with code whose maintainer is very explicitly offline. 

  A> * add in things like user configuration of the path to the 
  A> `pil` executable.  :-)" 

 TJ> AFAIK the path is remembered, to avoid typing, but can be 
 TJ> changed - just try using a prefix before the command, that 
 TJ> should give you the opportunity to type in your own path 
 TJ> (but I'm not sure right now). 

 TJ> Try C-h f on the core functions, there is quite a lot of 
 TJ> info in the docstrings. 

Here's the doc for `run-picolisp` (which, i note, isn't mentioned 
in the README; nor does it begin with the `picolisp-` prefix to 
assist its discoverability and limit namespacing issues) from the 
GitHub version: 

   run-picolisp is an interactive autoloaded Lisp function in 
   `inferior-picolisp.el'. 

   It is bound to . 

   (run-picolisp CMD) 

   Run an inferior Picolisp process, input and output via buffer 
   `*picolisp*'.  If there is a process already running in 
   `*picolisp*', switch to that buffer.  With argument, allows 
   you to edit the command line (default is value of 
   `picolisp-program-name').  Runs the hook 
   `inferior-picolisp-mode-hook' (after the `comint-mode-hook' is 
   run).  (Type C-h m in the process buffer for a list of 
   commands.) 

The fact that one can add a prefix arg to it to specify the full 
path to the `pil` executable, and that such a specification will 
be automatically remembered, isn't mentioned. 


 TJ> Sorry for being late to the discussion, but I'm
 TJ> not really online at the moment.

Fair enough; life happens! i myself have a lot happening, so it's 
important to me that my FOSS contributions aren't to no effect, or 
become more complex to manage than i've got the time and energy 
for. Consequently, given that the more i look at the situation 
around the above implementations, the more contextual 
complexity[1] i find, i feel it's best for someone else to take on 
the work of sorting things out.


[1] As distinct from any complexity in the code itself.

At any rate, i've started the process of renaming my own `picolisp-mode`
to `a-picolisp-mode`, so that it doesn't get confused with these other
existing codebases; and in the README for my package, i'll be
emphasising that my code is in no way connected with the PicoLisp
support included in the PicoLisp distribution, or the modified version
thereof available on GitHub.


Alexis.
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Re: Installation issues

[Henrik Sarvell]

To complicate things I've attached my two local versions of picolisp.el and
inferior-picolisp.el

When I diff them I see quite substantial differences.

Unfortunately I have no idea why I made those changes as I didn't take any
notes and it was several years ago.



On Tue, Feb 17, 2015 at 7:12 AM, Alexander Burger 
wrote:

> Hi list,
>
> as I mentioned in my previous mail, is Thorsten currently offline.
> He asked me to post this for him:
>
> -
> Hi Alexis,
> this is Thorsten, the current maintainer (but ot original author) of
> the Emacs stuff.
>
> "i'll try to find some time to:
>
>
> * examine the diffs between the distribution version and the GitHub
> version;
> Why? Just use the newer version, i.e. the Github version. Nobody else but
> me did change anything recently.
>
> * add to the former any fixes and/or extra functionality found in the
> latter;
> Again - why? Just replace the older version with the newer version ...
>
>
> * add in my code to present documentation for the symbol at point; and
> you mean an eldoc implementation for picolisp? patches are welcome, just
> fork me on github.
>
> * add in things like user configuration of the path to the `pil`
> executable.
> :-)"
> AFAIK the path is remembered, to avoid typing, but can be changed - just
> try using a prefix before the command, that should give you the opportunity
> to type in your own path (but I'm not sure right now).
>
> Try C-h f on the core functions, there is quite a lot of info in the
> docstrings.
> Sorry for being late to the discussion, but I'm not really online at the
> moment.
>
> Cheers
> Thorsten
> --
> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
>
;; picolisp-mode: Major mode to edit picoLisp.
;; Version: 1.1

;;; Copyright (c) 2009, Guillermo R. Palavecino

;; This file is NOT part of GNU emacs.

 Credits:
;; It's based on GNU emacs' lisp-mode and scheme-mode.
;; Some bits were taken from paredit.el
;;
 Contact:
;; For comments, bug reports, questions, etc, you can contact me via IRC
;; to the user named grpala (or armadillo) on irc.freenode.net in the
;; #picolisp channel or via email to the author's nickname at gmail.com
;;
 License:
;; This work is released under the GPL 2 or (at your option) any later
;; version.

(require 'lisp-mode)

(defcustom picolisp-parsep t
  "This is to toggle picolisp-mode's multi-line s-exps closing parens separation capability."
  :type 'boolean
  :group 'picolisp )

;; I know... this shouldn't be here, but you see, people may want to keep
;; their body-indent value unaltered and have a different one for picolisp
;; sources, so...
(defcustom picolisp-body-indent 3
  "Number of columns to indent the second line of a `(de ...)' form."
  :group 'picolisp
  :type 'integer )

(defvar picolisp-mode-syntax-table
  (let ((st (make-syntax-table))
(i 0) )

;; Default is atom-constituent.
(while (< i 256)
  (modify-syntax-entry i "_   " st)
  (setq i (1+ i)) )

;; Word components.
(setq i ?0)
(while (<= i ?9)
  (modify-syntax-entry i "w   " st)
  (setq i (1+ i)) )
(setq i ?A)
(while (<= i ?Z)
  (modify-syntax-entry i "w   " st)
  (setq i (1+ i)) )
(setq i ?a)
(while (<= i ?z)
  (modify-syntax-entry i "w   " st)
  (setq i (1+ i)) )

;; Whitespace
(modify-syntax-entry ?\t "" st)
(modify-syntax-entry ?\n ">   " st)
(modify-syntax-entry ?\f "" st)
(modify-syntax-entry ?\r "" st)
(modify-syntax-entry ?\s "" st)

;; These characters are delimiters but otherwise undefined.
;; Brackets and braces balance for editing convenience.
(modify-syntax-entry ?\[ "(]  " st)
(modify-syntax-entry ?\] ")[  " st)
(modify-syntax-entry ?{  "(}  " st)
(modify-syntax-entry ?}  "){  " st)

;; Other atom delimiters
(modify-syntax-entry ?\( "()  " st)
(modify-syntax-entry ?\) ")(  " st)
;; It's used for single-line comments.
(modify-syntax-entry ?#  "<   " st)
(modify-syntax-entry ?\" "\"   " st)
(modify-syntax-entry ?'  "'   " st)
(modify-syntax-entry ?`  "'   " st)
(modify-syntax-entry ?~  "'   " st)

;; Special characters
(modify-syntax-entry ?,  "'   " st)
(modify-syntax-entry ?\\ "\\   " st)
st ) )

(defvar picolisp-mode-abbrev-table nil)
(define-abbrev-table 'picolisp-mode-abbrev-table ())

(defun picolisp-mode-variables ()
  (set-syntax-table picolisp-mode-syntax-table)
  ;;(setq local-abbrev-table picolisp-mode-abbrev-table)
  (make-local-variable 'paragraph-start)
  (setq paragraph-start (concat "$\\|" page-delimiter))
  ;;(setq comint-input-ring-file-name "~/.pil_history")

  (make-local-variable 'paragraph-separate)
  (setq paragraph-separate paragraph-start)

  (make-local-variable 'paragraph-ignore-fill-prefix)
  (setq paragraph-ignore-fill-prefix t)

  (make-local-variable 'fill-paragraph-function)
  (setq fill-paragraph-function 'lisp-fill-

Re: Installation issues

[Alexander Burger]

Hi list,

as I mentioned in my previous mail, is Thorsten currently offline.
He asked me to post this for him:

-
Hi Alexis,
this is Thorsten, the current maintainer (but ot original author) of
the Emacs stuff.

"i'll try to find some time to:


* examine the diffs between the distribution version and the GitHub
version;
Why? Just use the newer version, i.e. the Github version. Nobody else but
me did change anything recently.

* add to the former any fixes and/or extra functionality found in the
latter;
Again - why? Just replace the older version with the newer version ...


* add in my code to present documentation for the symbol at point; and
you mean an eldoc implementation for picolisp? patches are welcome, just
fork me on github.

* add in things like user configuration of the path to the `pil` executable.
:-)"
AFAIK the path is remembered, to avoid typing, but can be changed - just
try using a prefix before the command, that should give you the opportunity
to type in your own path (but I'm not sure right now).

Try C-h f on the core functions, there is quite a lot of info in the
docstrings.
Sorry for being late to the discussion, but I'm not really online at the
moment.

Cheers
Thorsten
-- 
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Re: Installation issues

[Alexis]

On 2015-02-15T02:56:38+1100, Alexander Burger said:

AB> Unfortunately, Thorsten (the original maintainer) is 
currently AB> offline.


AB> I can't do anything in 'picolisp.el', as I'm ignorant of 
emacs, AB> but I can gladly take changes (if they are 
thoughtfully reviewed AB> and agreed upon by competent people) 
and put them into the AB> PicoLisp release.


Excellent. :-) Thanks!

i'll try to find some time to:

* examine the diffs between the distribution version and the 
 GitHub version;


* add to the former any fixes and/or extra functionality found 
 in the latter;


* add in my code to present documentation for the symbol at 
 point; and


* add in things like user configuration of the path to the `pil` 
 executable. :-)



Alexis.
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Re: Installation issues

[Alexander Burger]

Hi Alexis,

> >Hi Alexis, if I google "picolisp emacs" I see the following URL as
> >the #1 result: https://github.com/tj64/picolisp-mode
> >
> >That is what I use when I code PL in Emacs, works great!
> 
> Excellent. :-) However, that code hasn't been updated for over 2
> years, and since i've had a few bad experiences recently with
> unmaintained code (bug reports and pull requests ignored, even by
> ...
> PicoLisp site itself. Although - is `picolisp.el` actively
> maintained?  Possible copyright issues aside, would proposed patches
> be reviewed / accepted?

Unfortunately, Thorsten (the original maintainer) is currently offline.

I can't do anything in 'picolisp.el', as I'm ignorant of emacs, but I
can gladly take changes (if they are thoughtfully reviewed and agreed
upon by competent people) and put them into the PicoLisp release.

♪♫ Alex
-- 
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Re: Installation issues

[Alexis]

On 2015-02-14T00:39:55+1100, Lawrence Bottorff said:

LB> Is this different from the distribution version?

Yes. The distribution version includes `picolisp-wiki-mode.el`, 
which the GitHub version doesn't, and a running a diff on 
`picolisp.el` and `inferior-picolisp.el` shows various 
differences; i've included the diff outputs at the end of this 
message. The files with -1 in their name are from the GitHub 
version, the files with -2 in their name are from the distribution 
version.


LB> BTW, the dist version doesn't seem to have a customize - mode 
LB> variable for the picolisp exe or for pil. Again, the default 
seems LB> to be /usr/bin/pil . How do I override this?


i guess the easiest thing to do would be to open 
`inferior-picolisp.el` and modify the following line such that the 
text "pil" is replaced with the full path to the `pil` executable:


(defvar picolisp-program-name "pil +" 
 "The name of the program used to run Picolisp." ) 


which for you would result in:

(defvar picolisp-program-name "/home/lawrence/opt/picoLisp/pil +" 
 "The name of the program used to run Picolisp." ) 



Alexis.


*** BEGIN DIFFS ***

** picolisp-1.el vs. picolisp-2.el **

27c27 <  --- 
 
98c98 <  --- 
 
199c199 <  --- 
 
243c243 <  --- 
 
285c285 <  --- 
 
378c378 <  --- 
 
396c396 <  --- 
 
498c498 <  --- 
 
539c539 <  --- 
 
582c582 <  --- 
 
617c617,618 <   (let* ((unit (get-selection-or-unit 'word)) 
--- 
  (let* ((thing (thing-at-point 'word))   
 (unit (get-selection-or-unit 'word)) 
645c646 <  --- 
 
751c752 <  --- 
 


** inferior-picolisp-1.el vs. inferior-picolisp-2.el

1,22c1,2 < ;; * inferior-picolisp.el --- picolisp repl in a buffer 
< ;; ** MetaData < ;;   :PROPERTIES: < ;;   :copyright: 
Guillermo_R._Palavecino Thorsten_Jolitz < ;;   :copyright-since: 
2009 < ;;   :version:  1.2 < ;;   :licence:  GPL2+ < ;; 
:licence-url: http://www.gnu.org/licenses/ < ;;   :part-of-emacs: 
no < ;;   :git-repo: https://github.com/tj64/iorg < ;; 
:git-clone: g...@github.com:tj64/iorg.git < ;;   :authors: 
Guillermo_R._Palavecino Thorsten_Jolitz < ;;   :contact: 
  < ;;   :inspiration: 
cmuscheme.el < ;;   :keywords: emacs picolisp comint repl iorg < 
;;   :END: <  < ;; ** Commentary <  < ;; For comments, bug 
reports, questions, etc use the picolisp mailing list, < ;; the 
#picolisp channel on irc.freenode.net, or the author's emails 
given < ;; above.  --- 
;; inferior-picolisp: Picolisp repl in a buffer.  ;; 
Version: 1.2 
24c4,18 < ;; * Requires --- 
;;; Copyright (c) 2009, 2012, 2013, Guillermo R. Palavecino, 
Thorsten Jolitz  ;; This file is NOT part of GNU emacs.    
Credits: ;; It's and adaptation of GNU emacs' cmuscheme.el ;; 
 Contact: ;; For comments, bug reports, questions, etc, you 
can contact me via IRC ;; to the user named grpala (or 
armadillo) on irc.freenode.net in the ;; #picolisp channel or 
via email to the author's nickname at gmail.com ;;  License: 
;; This work is released under the GPL 2 or (at your option) any 
later ;; version. 
29,30d22 < ;; * Mode definitions < ;; ** Inferior Picolisp Mode 
32,33c24,26 < (define-derived-mode inferior-picolisp-mode 
comint-mode "Inferior Picolisp" <   "Major mode for interacting 
with an inferior Picolisp process.  --- 
(defgroup picolisp nil 
  "Run an Picolisp process in a buffer."  :group 'picolisp ) 
35,36c28,29 < The following commands are available: < 
\\{inferior-picolisp-mode-map} --- 
;;; INFERIOR PICOLISP MODE STUFF 
;;; 
38c31,32 < An Picolisp process can be fired up with 'M-x 
run-picolisp'.  --- 
(defconst inferior-picolisp-version "1.2" 
  "Verion-number of library") 
40,41c34,37 < Customization: Entry to this mode runs the hooks on 
`comint-mode-hook' and < `inferior-picolisp-mode-hook' (in that 
order).  --- 
(defcustom inferior-picolisp-mode-hook nil 
  "*Hook for customizing inferior-picolisp mode."  :type 'hook 
  :group 'picolisp ) 
43,44c39,44 < You can send text to the inferior Picolisp process 
from other < buffers containing Picolisp source.  --- 
(defvar inferior-picolisp-mode-map 
  (let ((m (make-sparse-keymap))) 
(define-key m "\M-\C-x" 'picolisp-send-definition) ;gnu 
convention (define-key m "\C-x\C-e" 
'picolisp-send-last-sexp) (define-key m "\C-c\C-l" 
'picolisp-load-file) m ) ) 
46,47c46,47 <  - `switch-to-picolisp' switches the current buffer 
to the 

Re: Installation issues

[Alexis]

Henrik Sarvell writes:

Hi Alexis, if I google "picolisp emacs" I see the following URL 
as the #1 result: https://github.com/tj64/picolisp-mode


That is what I use when I code PL in Emacs, works great!


Excellent. :-) However, that code hasn't been updated for over 2 
years, and since i've had a few bad experiences recently with 
unmaintained code (bug reports and pull requests ignored, even by 
people still definitely actively coding), i'd rather not develop a 
workflow that relies on such code.


Having said that, to me it also demonstrates that the presence of 
PicoLisp support in the standard distribution should be noted on 
the PicoLisp site itself. Although - is `picolisp.el` actively 
maintained?  Possible copyright issues aside, would proposed 
patches be reviewed / accepted?



Alexis.
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Re: Installation issues

[Henrik Sarvell]

Hi Lawrence, I have no idea, I have never installed the dist version.

I usually install like at the bottom of this article:
http://picolisp.com/wiki/?Websockets

On Fri, Feb 13, 2015 at 2:39 PM, Lawrence Bottorff 
wrote:

> Is this different from the distribution version? BTW, the dist version
> doesn't seem to have a customize - mode variable for the picolisp exe or
> for pil. Again, the default seems to be /usr/bin/pil . How do I override
> this?
>

Re: Installation issues

[Lawrence Bottorff]

Is this different from the distribution version? BTW, the dist version
doesn't seem to have a customize - mode variable for the picolisp exe or
for pil. Again, the default seems to be /usr/bin/pil . How do I override
this?

Re: Installation issues

[Henrik Sarvell]

Hi Alexis, if I google "picolisp emacs" I see the following URL as the #1
result: https://github.com/tj64/picolisp-mode

That is what I use when I code PL in Emacs, works great! I've added a few
keywords to the mode and the doc jumping in my init.el, could post both
changes here if anyone is interested.



On Fri, Feb 13, 2015 at 1:05 AM, Alexis  wrote:

>
> andr...@itship.ch writes:
>
>  @Alexis: Just have a look into lib/el/ in your picolisp installation.
>>
>
> i'm on Debian Wheezy(+updates), and having installed the available
> PicoLisp package (3.1.0.7-1), couldn't see any .el files within the
> PicoLisp directory (/usr/share/picolisp/), which doesn't have a /lib or
> /lib/el directory either. However, having downloaded the 3.1.9 tarball and
> unpacked it, i can now see the files you're talking about.
>
> Have i missed in the documentation where support for editing in Emacs is
> mentioned? From:
>
> http://picolisp.com/wiki/?Documentation
>
> i can't see any mention of it in any of:
>
> * Manual Page
> * Reference Manual
> * Common Index
> * README
> * INSTALL
> or
> * FAQ
>
> ...
>
>  Maybe your efforts aren't really necessary (but surely a good exercise
>> anyway).
>> ...
>> Maybe you should rename your emacs extensions, so it doesn't get mixed up
>> with the one coming with the picolisp standard distribution.
>>
>
> Well, if i'd known that Emacs support was already available, i wouldn't
> have written my package in the first place! i already maintain a couple of
> other Emacs packages, and have lots of other coding i'd like to be doing,
> so i only worked on my PicoLisp package to help myself and other Emacs
> users, rather than to learn about writing and/or packaging Emacs Lisp - the
> package as it currently stands didn't require extensive knowledge of
> PicoLisp.
>
> Now that i know comprehensive Emacs support for PicoLisp is available,
> i'll probably just remove my own PicoLisp package from MELPA. The only
> thing that my package provides that the distribution package doesn't - as
> far as i can tell! - is support for showing documentation for the symbol at
> point, either in a browser or in Emacs itself. i'd be happy for my code for
> that to be added to the distribution package, assuming i don't have to sign
> any paperwork to do so 
>
>
>
> Alexis.
> --
> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
>

Re: Installation issues

[Alexis]

andr...@itship.ch writes:

@Alexis: Just have a look into lib/el/ in your picolisp 
installation.


i'm on Debian Wheezy(+updates), and having installed the available 
PicoLisp package (3.1.0.7-1), couldn't see any .el files within 
the PicoLisp directory (/usr/share/picolisp/), which doesn't have 
a /lib or /lib/el directory either. However, having downloaded the 
3.1.9 tarball and unpacked it, i can now see the files you're 
talking about.


Have i missed in the documentation where support for editing in 
Emacs is mentioned? From:


http://picolisp.com/wiki/?Documentation

i can't see any mention of it in any of:

* Manual Page
* Reference Manual
* Common Index
* README
* INSTALL
or
* FAQ

...

Maybe your efforts aren't really necessary (but surely a good 
exercise anyway).

...
Maybe you should rename your emacs extensions, so it doesn't get 
mixed up with the one coming with the picolisp standard 
distribution.


Well, if i'd known that Emacs support was already available, i 
wouldn't have written my package in the first place! i already 
maintain a couple of other Emacs packages, and have lots of other 
coding i'd like to be doing, so i only worked on my PicoLisp 
package to help myself and other Emacs users, rather than to learn 
about writing and/or packaging Emacs Lisp - the package as it 
currently stands didn't require extensive knowledge of PicoLisp.


Now that i know comprehensive Emacs support for PicoLisp is 
available, i'll probably just remove my own PicoLisp package from 
MELPA. The only thing that my package provides that the 
distribution package doesn't - as far as i can tell! - is support 
for showing documentation for the symbol at point, either in a 
browser or in Emacs itself. i'd be happy for my code for that to 
be added to the distribution package, assuming i don't have to 
sign any paperwork to do so 



Alexis.
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Re: Installation issues

[andreas]

The drop-down menu has tools to do indentation, commenting in and out, and to run-picolisp.When you have  run-picolisp started (thats an emacs buffer with pil repl), there are several additional options in the dropdown to evaluate the picolisp code where the cursor is in the editor buffer, or to run marked s-expressions.You might be also interested in using emacs-like editing within the pil-repl:  http://picolisp.com/wiki/?emacsstyleled @Alexis:Just have a look into lib/el/ in your picolisp installation. Maybe your efforts aren't really necessary (but surely a good exercise anyway).I'm using the picolisp-mode coming with the picolisp distribution, and I'm really happy with it, especially since I use "paredit" with it.Though I actually don't use the provided pil repl inside emacs but an additional terminal window (with http://i3wm.org).Maybe you should rename your emacs extensions, so it doesn't get mixed up with the one coming with the picolisp standard distribution.- Original Message - From: Lawrence Bottorff [mailto:borg...@gmail.com] To: picolisp@software-lab.de Sent: Thu, 12 Feb 2015 08:24:11 -0500 Subject: 
Okay, now it's working! Thanks for all your efforts!
 
As far as the drop-down menu, I can't recall. But it was present with the distribution package, in .../lib/el if I'm not mistaken. It's just that now when I run M-x picolisp-mode . . . nothing seems to have happened. For opening a *.l file, I get "Lisp Paredit Slime Projectile[picolisp] adoc" in my mode minibuffer. The original picolisp-mode.el instructions warned that *.l would be grabbed by slime. . . .


On Thu, Feb 12, 2015 at 6:54 AM, Alexis  wrote:


 Lawrence Bottorff writes: 
Okay, this is what I get with the latest melpa picolisp-mode:  emacs-snapshot: /usr/bin/pil: No such file or directory  Process picolisp-repl exited abnormally with code 127


This is /after/ you've set the value of `picoliso-pil-executable` appropriately?

   Alexis. --  UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Re: Installation issues

[Lawrence Bottorff]

Okay, now it's working! Thanks for all your efforts!

As far as the drop-down menu, I can't recall. But it was present with the
distribution package, in .../lib/el if I'm not mistaken. It's just that now
when I run M-x picolisp-mode . . . nothing seems to have happened. For
opening a *.l file, I get "Lisp Paredit Slime Projectile[picolisp] adoc" in
my mode minibuffer. The original picolisp-mode.el instructions warned that
*.l would be grabbed by slime. . . .

On Thu, Feb 12, 2015 at 6:54 AM, Alexis  wrote:

>
> Lawrence Bottorff writes:
>
>  Okay, this is what I get with the latest melpa picolisp-mode:
>>
>> emacs-snapshot: /usr/bin/pil: No such file or directory
>>
>> Process picolisp-repl exited abnormally with code 127
>>
>
> This is /after/ you've set the value of `picoliso-pil-executable`
> appropriately?
>
>
>
> Alexis.
> --
> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
>

Re: Installation issues

[Alexis]

Lawrence Bottorff writes:


Okay, this is what I get with the latest melpa picolisp-mode:

emacs-snapshot: /usr/bin/pil: No such file or directory

Process picolisp-repl exited abnormally with code 127


This is /after/ you've set the value of `picoliso-pil-executable` 
appropriately?



Alexis.
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Re: Installation issues

[Alexis]

Lawrence Bottorff writes:

BTW, I don't see a drop-down menu when I start 
picolisp-mode. The old version (bundled with the picolisp 
download had one. Just thought I'd mention it. . . .


Well, what i've written isn't any sort of 'update' of the version 
you mention; i wrote it from scratch, as i wasn't aware of any 
other actively-maintained Emacs support for PicoLisp. :-)


What sort of functionality did the drop-down menu provide? i'm 
happy to work on feature requests 



Alexis.
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Re: Installation issues

[Lawrence Bottorff]

Okay, this is what I get with the latest melpa picolisp-mode:

emacs-snapshot: /usr/bin/pil: No such file or directory

Process picolisp-repl exited abnormally with code 127

>
>

Re: Installation issues

[Lawrence Bottorff]

BTW, I don't see a drop-down menu when I start picolisp-mode. The old
version (bundled with the picolisp download had one. Just thought I'd
mention it. . . .

On Thu, Feb 12, 2015 at 6:18 AM, Lawrence Bottorff 
wrote:

> Forward-step (Fortschritt) must be, so said Wallenski.
>
> On Wed, Feb 11, 2015 at 10:56 PM, Alexis  wrote:
>
>>
>> Alexis writes:
>>
>>  Lawrence Bottorff writes:
>>>
>>
>>   . . I'm sure if I install a ubuntu-debian package version of  picolisp
 (3.1.7) picolisp-repl will see that, i.e., it's hardwired somewhere to look
 for a /usr/bin/ executable (pil or picolisp).

>>>
>>  Not quite: the problem turns out to be that i've failed to make use of
>>> the `picolisp-pil-executable` variable in `picolisp-repl`,  such that `pil`
>>> is only searched for in whatever paths have been  specified in Emacs'
>>> execution environment. Sorry! i'll fix that  now.
>>>
>>
>> i've now pushed the correction to GitHub; the corrected version should be
>> available from MELPA within an hour or so (if not sooner).
>>
>> Sorry again for the hassle, and thanks for finding this issue!
>>
>>
>>
>> Alexis.
>> --
>> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
>>
>
>

Re: Installation issues

[Lawrence Bottorff]

Forward-step (Fortschritt) must be, so said Wallenski.

On Wed, Feb 11, 2015 at 10:56 PM, Alexis  wrote:

>
> Alexis writes:
>
>  Lawrence Bottorff writes:
>>
>
>   . . I'm sure if I install a ubuntu-debian package version of  picolisp
>>> (3.1.7) picolisp-repl will see that, i.e., it's hardwired somewhere to look
>>> for a /usr/bin/ executable (pil or picolisp).
>>>
>>
>  Not quite: the problem turns out to be that i've failed to make use of
>> the `picolisp-pil-executable` variable in `picolisp-repl`,  such that `pil`
>> is only searched for in whatever paths have been  specified in Emacs'
>> execution environment. Sorry! i'll fix that  now.
>>
>
> i've now pushed the correction to GitHub; the corrected version should be
> available from MELPA within an hour or so (if not sooner).
>
> Sorry again for the hassle, and thanks for finding this issue!
>
>
>
> Alexis.
> --
> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
>

Re: Installation issues

[Alexis]

Alexis writes:

Lawrence Bottorff writes: 


 . . I'm sure if I install a ubuntu-debian package version of 
 picolisp  
(3.1.7) picolisp-repl will see that, i.e., it's hardwired 
somewhere to look for a /usr/bin/ executable (pil or picolisp). 


Not quite: the problem turns out to be that i've failed to make 
use of the `picolisp-pil-executable` variable in 
`picolisp-repl`,  such that `pil` is only searched for in 
whatever paths have been  specified in Emacs' execution 
environment. Sorry! i'll fix that  now. 


i've now pushed the correction to GitHub; the corrected version 
should be available from MELPA within an hour or so (if not 
sooner).


Sorry again for the hassle, and thanks for finding this issue!


Alexis.
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Re: Installation issues

[Alexis]

Lawrence Bottorff writes:

 . . I'm sure if I install a ubuntu-debian package version of 
 picolisp 
(3.1.7) picolisp-repl will see that, i.e., it's hardwired 
somewhere to look for a /usr/bin/ executable (pil or picolisp).


Not quite: the problem turns out to be that i've failed to make 
use of the `picolisp-pil-executable` variable in `picolisp-repl`, 
such that `pil` is only searched for in whatever paths have been 
specified in Emacs' execution environment. Sorry! i'll fix that 
now.



Alexis.
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Re: Installation issues

[Alexis]

Lawrence Bottorff writes:


No matter what I do, M-x picolisp-repl gives:

 Searching for program: no such file or directory, pil

I've set customize group thus: .. 
'(picolisp-picolisp-executable 
"/home/lawrence/opt/picoLisp/bin/picolisp") 
 '(picolisp-pil-executable "/home/lawrence/opt/picoLisp/pil")


in a fresh install of the melpa picolisp-mode.

Help?


Could you please show the context surrounding the above settings?

Do things work if you go to the *scratch* buffer, enter:

(setq picolisp-pil-executable "/home/lawrence/opt/picoLisp/pil")

and then evaluate that with C-x C-e?

(On my system, the `pil` script is actually in /usr/bin/.)


Alexis.
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Re: Installation issues

[Lawrence Bottorff]

 . . I'm sure if I install a ubuntu-debian package version of picolisp
(3.1.7) picolisp-repl will see that, i.e., it's hardwired somewhere to look
for a /usr/bin/ executable (pil or picolisp).

On Wed, Feb 11, 2015 at 10:21 PM, Lawrence Bottorff 
wrote:

> No matter what I do, M-x picolisp-repl gives:
>
>  Searching for program: no such file or directory, pil
>
> I've set customize group thus:
> ...
> '(picolisp-picolisp-executable "/home/lawrence/opt/picoLisp/bin/picolisp")
>  '(picolisp-pil-executable "/home/lawrence/opt/picoLisp/pil")
>
> in a fresh install of the melpa picolisp-mode.
>
> Help?
>
>
>
> On Wed, Feb 11, 2015 at 8:29 PM, Alexis  wrote:
>
>>
>> Lawrence Bottorff writes:
>>
>>  New install. Put picoLisp in ~/opt/picoLisp/ Then I created an alias for
>>> the pil:
>>>
>>> alias pil='~/opt/picoLisp/pil +'
>>>
>>> This works fine from shell; starts up REPL. However emacs can't start
>>> the REPL (run-picolisp):
>>>
>>> Searching for program: no such file or directory, pil
>>>
>>> What can I do to make emacs see ~/opt/picoLisp/pil  ?
>>>
>>
>> i'm running a manually-compiled Emacs 24.4, and i don't have any
>> `run-picolisp` command available - what version of Emacs are you using?
>>
>> In any event, you might be interested in using the `picolisp-mode`
>> package i've started developing:
>>
>> https://github.com/flexibeast/picolisp-mode
>>
>> You can specify the location of the `pil` executable via the `picolisp`
>> customize-group, or by setting the value of `picolisp-pil-executable`.
>>
>>
>> Alexis.
>> --
>> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
>>
>
>

Re: Installation issues

[Lawrence Bottorff]

No matter what I do, M-x picolisp-repl gives:

 Searching for program: no such file or directory, pil

I've set customize group thus:
..
'(picolisp-picolisp-executable "/home/lawrence/opt/picoLisp/bin/picolisp")
 '(picolisp-pil-executable "/home/lawrence/opt/picoLisp/pil")

in a fresh install of the melpa picolisp-mode.

Help?



On Wed, Feb 11, 2015 at 8:29 PM, Alexis  wrote:

>
> Lawrence Bottorff writes:
>
>  New install. Put picoLisp in ~/opt/picoLisp/ Then I created an alias for
>> the pil:
>>
>> alias pil='~/opt/picoLisp/pil +'
>>
>> This works fine from shell; starts up REPL. However emacs can't start the
>> REPL (run-picolisp):
>>
>> Searching for program: no such file or directory, pil
>>
>> What can I do to make emacs see ~/opt/picoLisp/pil  ?
>>
>
> i'm running a manually-compiled Emacs 24.4, and i don't have any
> `run-picolisp` command available - what version of Emacs are you using?
>
> In any event, you might be interested in using the `picolisp-mode` package
> i've started developing:
>
> https://github.com/flexibeast/picolisp-mode
>
> You can specify the location of the `pil` executable via the `picolisp`
> customize-group, or by setting the value of `picolisp-pil-executable`.
>
>
> Alexis.
> --
> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
>

Re: Installation issues

[Alexis]

Lawrence Bottorff writes:

New install. Put picoLisp in ~/opt/picoLisp/ Then I created an 
alias for the pil:


alias pil='~/opt/picoLisp/pil +'

This works fine from shell; starts up REPL. However emacs can't 
start the REPL (run-picolisp):


Searching for program: no such file or directory, pil

What can I do to make emacs see ~/opt/picoLisp/pil  ?


i'm running a manually-compiled Emacs 24.4, and i don't have any 
`run-picolisp` command available - what version of Emacs are you 
using?


In any event, you might be interested in using the `picolisp-mode` 
package i've started developing:


https://github.com/flexibeast/picolisp-mode

You can specify the location of the `pil` executable via the 
`picolisp` customize-group, or by setting the value of 
`picolisp-pil-executable`.



Alexis.
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Re: Installation issues

[Tomas Hlavaty]

Hi Lawrence,

> alias pil='~/opt/picoLisp/pil +'
>
> This works fine from shell; starts up REPL However emacs can't
> start the REPL (run-picolisp):
>
> Searching for program: no such file or directory, pil
>
> What can I do to make emacs see ~/opt/picoLisp/pil  ?

have you tried

   alias pil=~/opt/picoLisp/pil

i.e. just the path to the program?

Cheers,

Tomas
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Re: Installation issues

[Lawrence Bottorff]

New install. Put picoLisp in ~/opt/picoLisp/ Then I created an alias for
the pil:

alias pil='~/opt/picoLisp/pil +'

This works fine from shell; starts up REPL. However emacs can't start the
REPL (run-picolisp):

Searching for program: no such file or directory, pil

What can I do to make emacs see ~/opt/picoLisp/pil  ?

LB


On Mon, Feb 9, 2015 at 10:27 AM, Loyall, David 
wrote:

> For what it is worth, here are the contents of every file named 'pil' in
> the 3.1.9 tarball.
>
> hobbes@metalbaby:~/src/pil319/picoLisp$ find . -name pil -exec head -1000
> {} +
> ==> ./bin/pil <==
> #!/usr/bin/picolisp /usr/lib/picolisp/lib.l
> (load "@lib/misc.l" "@lib/btree.l" "@lib/db.l" "@lib/pilog.l")
>
> ==> ./ersatz/pil <==
> #!/bin/sh
> # 29nov10abu
>
> # Run Ersatz PicoLisp
> exec java -DPID=$$ -cp .:tmp:${0%/*}/picolisp.jar PicoLisp ${0%/*}/lib.l
> "$@"
>
> ==> ./pil <==
> #!/bin/sh
> exec ${0%/*}/bin/picolisp ${0%/*}/lib.l @ext.l "$@"
>
> NB the one that explicitly calls /usr/bin/picolisp (which is probably
> still the one installed by your package manager) and interprets the rest of
> the file as lisp source.
>
> Cheers,
> --Dave
>
> p.s. Here's what I use for my interactive REPL:
>
> hobbes@metalbaby:~/src/mb.pl.emu$ cat pil
> #!/bin/sh
> BROWSER=x-www-browser exec ${0%/*}/bin/picolisp ${0%/*}/lib.l @ext.l
> @lib/misc.l @lib/btree.l @lib/db.l @lib/pilog.l "$@"
>
> > -Original Message-
> > From: picolisp@software-lab.de [mailto:picolisp@software-lab.de] On
> Behalf
> > Of Alexander Burger
> > Sent: Saturday, February 07, 2015 12:29 AM
> > To: picolisp@software-lab.de
> > Subject: Re: Installation issues
> >
> > Hi Lawrence,
> >
> > > I've gotten the latest picolisp, 3.1.9, and am trying to install
> locally.
> >
> > OK
> >
> > > Following the instructions for 64-bit on my linux, I've built the
> > > executable picolisp all right. But the bin directory's pil seems to
> > > pick up the previous version I installed before from Ubuntu:
> >
> > I think I know what the problem is. It may be that the wrong 'pil' is
> executed,
> > because there is another one in /bin, which is intended
> for the
> > global installation.
> >
> > You need to install /pil, e.g.
> >
> >$ cd 
> >$ ./pil +
> >
> > (the '+' at the end is recommended, to get into debug mode).
> >
> > You can run it from any place, e.g. with an absolute path
> >
> >$ /path/to/my/installation/pil +
> >
> > or with a relative path
> >
> >$ ../../installation/pil +
> >
> > or whatever.
> >
> > ♪♫ Alex
>
>

RE: Installation issues

[Loyall, David]

For what it is worth, here are the contents of every file named 'pil' in the 
3.1.9 tarball.

hobbes@metalbaby:~/src/pil319/picoLisp$ find . -name pil -exec head -1000 {} +
==> ./bin/pil <==
#!/usr/bin/picolisp /usr/lib/picolisp/lib.l
(load "@lib/misc.l" "@lib/btree.l" "@lib/db.l" "@lib/pilog.l")

==> ./ersatz/pil <==
#!/bin/sh
# 29nov10abu

# Run Ersatz PicoLisp
exec java -DPID=$$ -cp .:tmp:${0%/*}/picolisp.jar PicoLisp ${0%/*}/lib.l "$@"

==> ./pil <==
#!/bin/sh
exec ${0%/*}/bin/picolisp ${0%/*}/lib.l @ext.l "$@"

NB the one that explicitly calls /usr/bin/picolisp (which is probably still the 
one installed by your package manager) and interprets the rest of the file as 
lisp source.

Cheers,
--Dave

p.s. Here's what I use for my interactive REPL:

hobbes@metalbaby:~/src/mb.pl.emu$ cat pil
#!/bin/sh
BROWSER=x-www-browser exec ${0%/*}/bin/picolisp ${0%/*}/lib.l @ext.l 
@lib/misc.l @lib/btree.l @lib/db.l @lib/pilog.l "$@"

> -Original Message-
> From: picolisp@software-lab.de [mailto:picolisp@software-lab.de] On Behalf
> Of Alexander Burger
> Sent: Saturday, February 07, 2015 12:29 AM
> To: picolisp@software-lab.de
> Subject: Re: Installation issues
> 
> Hi Lawrence,
> 
> > I've gotten the latest picolisp, 3.1.9, and am trying to install locally.
> 
> OK
> 
> > Following the instructions for 64-bit on my linux, I've built the
> > executable picolisp all right. But the bin directory's pil seems to
> > pick up the previous version I installed before from Ubuntu:
> 
> I think I know what the problem is. It may be that the wrong 'pil' is 
> executed,
> because there is another one in /bin, which is intended for the
> global installation.
> 
> You need to install /pil, e.g.
> 
>$ cd 
>$ ./pil +
> 
> (the '+' at the end is recommended, to get into debug mode).
> 
> You can run it from any place, e.g. with an absolute path
> 
>$ /path/to/my/installation/pil +
> 
> or with a relative path
> 
>$ ../../installation/pil +
> 
> or whatever.
> 
> ♪♫ Alex

PԔ � &j)mX�����zV�u�.n7�

Re: Installation issues

[Alexander Burger]

Hi Lawrence,

> I've gotten the latest picolisp, 3.1.9, and am trying to install locally.

OK

> Following the instructions for 64-bit on my linux, I've built the
> executable picolisp all right. But the bin directory's pil seems to pick up
> the previous version I installed before from Ubuntu:

I think I know what the problem is. It may be that the wrong 'pil' is
executed, because there is another one in /bin, which is
intended for the global installation.

You need to install /pil, e.g.

   $ cd 
   $ ./pil +

(the '+' at the end is recommended, to get into debug mode).

You can run it from any place, e.g. with an absolute path

   $ /path/to/my/installation/pil +

or with a relative path

   $ ../../installation/pil +

or whatever.

♪♫ Alex
-- 
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Re: Installation issues

[Alexander Burger]

On Fri, Feb 06, 2015 at 05:42:43PM -0500, Lawrence Bottorff wrote:
> Why does the pil in .../bin/ behave this way? I'd like both, but I guess I
> could uninstall one of them. . .

No, keeping both is fine. I do the same.

You can have as many installations on the system as you like. You simply
select one of they by calling it with either non-specified path
(global), or absolute or relative path (locals).

♪♫ Alex
-- 
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Re: Installation on PowerPC Mac running OS X 10.411

[Kyle Vandale]

Alex,

I think the problem is more with the fact that I am using a Mac and  
Xcode (not necessarily typical of Unix development tools) rather than  
Pico Lisp itself.  This is compounded by my being stuck in the past  
so to speak with a Power PC chip and OS X 10.4.  No worries, when I  
have the time I will try and pick through the errors.


Regards,
Kyle

Thanks
On Sep 21, 2009, at 12:15 AM, Alexander Burger wrote:


Hello Kyle,

So there are some things I must adjust; but I decided in the  
meantime to

take Jon Kleiser's advice and install an earlier version -
picoLisp-2.3.0.  Success!!!  Now I get to investigate pico Lisp  
while I

work on the above.


This is strange. I'd be very much interested why picoLisp-2.3.0 works
and later versions not. There should be no relevant changes.

Cheers,
- Alex
--
UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=unsubscribe



--
UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=unsubscribe

Re: Installation on PowerPC Mac running OS X 10.411

[Alexander Burger]

Hello Kyle,

> So there are some things I must adjust; but I decided in the meantime to 
> take Jon Kleiser's advice and install an earlier version -  
> picoLisp-2.3.0.  Success!!!  Now I get to investigate pico Lisp while I 
> work on the above.

This is strange. I'd be very much interested why picoLisp-2.3.0 works
and later versions not. There should be no relevant changes.

Cheers,
- Alex
-- 
UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=unsubscribe

Re: Installation on PowerPC Mac running OS X 10.411

[Kyle Vandale]

Hello all,

I wanted to give an update and let everyone know I have had some  
success:


Alex was correct I did not have gcc loaded.  Originally I had Xcode  
on this machine and forgot I had done an OS X reinstall.  (I am  
embarrassed about that.  My background is embedded programming with a  
given IDE.)


So I downloaded Xcode 2.5 (the last version of Xcode that will run  
under OS X Tiger 10.4).  The make process ran quite far; however  
there was an error.  I ran make again to focus on the latter.  Here  
it is:


gcc -o ../lib/ext -dynamiclib -undefined dynamic_lookup ext.o
ld: flag: -undefined dynamic_lookup can't be used with  
MACOSX_DEPLOYMENT_TARGET environment variable set to: 10.1
/usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/libtool: internal link  
edit command failed

make: *** [../lib/ext] Error 1
PowerBook-12in:~/picoLisp-2.3.7/src kyle$

So there are some things I must adjust; but I decided in the meantime  
to take Jon Kleiser's advice and install an earlier version -  
picoLisp-2.3.0.  Success!!!  Now I get to investigate pico Lisp while  
I work on the above.


Thanks Jon and everyone for your help.  I am looking forward to  
learning Pico Lisp.


Best regards,
Kyle


On Sep 14, 2009, at 7:07 AM,   wrote:


Kyle,

The GCC compiler is contained in a package called "xcode".

Cheers,

- Rand


= -- UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=unsubscribe


--
UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=unsubscribe

Re: Installation on PowerPC Mac running OS X 10.411

[Alexander Burger]

Hi Boh Yap,

> mac. The 1st thing to do is to have the Developer CD that came with
> the Mac installed. All the compilers and build tools are in there. In
> ...

Thanks for the info!


> have tried the 64bit picolisp, but won't compile on my 10.5.7.

Yep, this does not work yet. The problem is to find out how to get the
64-bit assembler running (if it is there at all). We hope that Snow
Leopard eventually will support 64-bit assembly.

Cheers,
- Alex
-- 
UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=unsubscribe

Re: Installation on PowerPC Mac running OS X 10.411

[Boh Yap]

hi all,

I have compile picolisp 2.3.x (at least 2.3.3 or later..) on a PPC
mac. The 1st thing to do is to have the Developer CD that came with
the Mac installed. All the compilers and build tools are in there. In
your case, it can't find gcc, so that might be the problem. If you
bought yr Mac earlier, you may need to download and upgrade the
Developer CD/SDK's. As I remember there being a transition from gcc3.x
to gcc4 made during towards the end of the 10.4.x versions that may
cause some problems.

I had it working on my PPC Mac, 10.4.9/10 before, but unfortunately,
that machine is now broken. I also remember having to tweak the shell
var MACOSX_DEPLOYMENT_TARGET to the actual OS version...

I'm sorry I'm typing all this from memory, as that machine is now 1/2
dead, well the screen went blank, I have'nt had time to see if I can
use an external monitor, and I don't have one to spare at the moment.

I'm typing this on an Intel Mac, and I've not got picolisp on this,
have tried the 64bit picolisp, but won't compile on my 10.5.7.
-- 
UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=unsubscribe

Re: Installation on PowerPC Mac running OS X 10.411

[Kyle Vandale]

Hello Alex,

I appreciate the help.  Yes, I think I am going to need to do some  
tweaking.  I am about to leave on a two day trip, but I am anxious to  
get back and start in on it.  The good news is it looks like there  
have been a lot of responses.  Thank you everyone.


Best regards,
Kyle


On Sep 14, 2009, at 4:09 AM, Alexander Burger wrote:


Hi Kyle,

welcome to the mailing list!


I am having a bit of a problem installing picolisp on a PowerPC Mac
running OS X 10.411.  Here is the command line output after  
running the

make command.


I'm afraid I'm not of much help, as I don't have a Mac myself. I was
hoping that some of the Mac users in this list would react :-(



PowerBook-12in:~/picoLisp-2.3.7/src kyle$ make picolisp
...
make: gcc: Command not found


This looks like you have no development environment installed. What
needs to be done on a Mac to install or configure the C compiler?


From all what I've noticed about PicoLisp on the Mac so far, I  
believe

it is a mess. The Mac obviously is not intended as a development
machine. You have to fiddle arould with variables like
MACOSX_DEPLOYMENT_TARGET (why doesn't the Mac find that out by  
itself?).


Anyway, I hope that some of the Mac users could supply something
helpful.

Cheers,
- Alex
--
UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=unsubscribe



--
UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=unsubscribe

Re: Installation on PowerPC Mac running OS X 10.411

[rand]

Kyle,

The GCC compiler is contained in a package called "xcode".

 Cheers,

- Rand


=
-- 
UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=unsubscribe

Re: Installation on PowerPC Mac running OS X 10.411

[Alexander Burger]

Hi Randall,

> in.  I don't think that picolisp will run on the PowerPC without some =
> work and I think no one has tried it

I think it used to run without problems, when Rick Hanson sent me the
'make' parameters back in 2006.

Only the 64-bit version (in assembly) will not run, as an explicit port
to the PowerPC would be necessary. The 32-bit C-version is quite
portable, and does not much care about the CPU.
-- 
UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=unsubscribe

Re: Installation on PowerPC Mac running OS X 10.411

[Jon Kleiser]

Hi,

The latest Pico Lisp I have built on my PowerPC Mac (w/10.4.11), seems to
be picoLisp-2.3.0.

/Jon

> Hello,
>
> I am having a bit of a problem installing picolisp on a PowerPC Mac
> running OS X 10.411.  Here is the command line output after running
> the make command.
>
> PowerBook-12in:~/picoLisp-2.3.7/src kyle$ make picolisp
> gcc -c -O2 -m32 -pipe -falign-functions -fomit-frame-pointer -fno-
> strict-aliasing -W -Wimplicit -Wreturn-type -Wunused -Wformat -
> Wuninitialized -Wstrict-prototypes -D_GNU_SOURCE  -
> D_FILE_OFFSET_BITS=64 -D_OS='"Darwin"' main.c
> make: gcc: Command not found
> make: *** [main.o] Error 127
>
>
> In the mail archive, I ran across a message mentioning a problem
> during installation on a PowerPC chip with OS 10.4.  (Title "Pico,
> simul/gl/Makefile on Mac (was OpenGL menus..." on  Mon, 07 Apr 2008
> 06:15:18 -0700)  However, I am sure if this problem and mine are
> related or not.
>
> Thanks for any help.
>
> Regards,
> Kyle
> --
> UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=unsubscribe
>


-- 
UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=unsubscribe

Re: Installation on PowerPC Mac running OS X 10.411

[rand]

Hi All,

I sent a detailed message this morning to the list, but apparently from an =
email address that I was not subscribed and the list server tossed it (corr=
ect so).  I'll resend it tonight when I have access to my computer aga=
in.  I don't think that picolisp will run on the PowerPC without some =
work and I think no one has tried it

Cheers,

- Rand

 

On Mon Sep 14  6:47 , Henrik Sarvell  sent:

PowerPc, is that the old Motorola CPU architecture? If s=
o then no, the

one I copied to was definitely an Intel machine.



>>Ubuntu current version<<

Do you mean 9.04 by that?



/Henrik





On Mon, Sep 14, 2009 at 12:00 PM, Alexander Burger  On Mon, Sep 14, 2009 at 11:43:31AM +0200, =
Henrik Sarvell wrote:

>> executable that I had compiled in Ubun=
tu Feisty (observe no later

>> versions of Ubuntu will work as the GC=
C is broken on them) to a Mac

>

> I didn't watch the gcc-situation for a whi=
le, but I compiled PicoLisp

> repeatedly on current versions of Ubuntu w=
ithout problems.

> --

> UNSUBSCRIBE: picolisp@software-lab.de','','','')">picoli=
s...@software-lab.de?subject=3DUnsubscribe

>

-- 

UNSUBSCRIBE: picol...@=
software-lab.de','','','')">picolisp@software-lab.de?subject=3D=
Unsubscribe


=
-- 
UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=unsubscribe

Re: Installation on PowerPC Mac running OS X 10.411

[Henrik Sarvell]

PowerPc, is that the old Motorola CPU architecture? If so then no, the
one I copied to was definitely an Intel machine.

>>Ubuntu current version<<
Do you mean 9.04 by that?

/Henrik


On Mon, Sep 14, 2009 at 12:00 PM, Alexander Burger  wrote:
> On Mon, Sep 14, 2009 at 11:43:31AM +0200, Henrik Sarvell wrote:
>> executable that I had compiled in Ubuntu Feisty (observe no later
>> versions of Ubuntu will work as the GCC is broken on them) to a Mac
>
> I didn't watch the gcc-situation for a while, but I compiled PicoLisp
> repeatedly on current versions of Ubuntu without problems.
> --
> UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=unsubscribe
>
-- 
UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=unsubscribe

Re: Installation on PowerPC Mac running OS X 10.411

[Alexander Burger]

On Mon, Sep 14, 2009 at 11:43:31AM +0200, Henrik Sarvell wrote:
> executable that I had compiled in Ubuntu Feisty (observe no later
> versions of Ubuntu will work as the GCC is broken on them) to a Mac

I didn't watch the gcc-situation for a while, but I compiled PicoLisp
repeatedly on current versions of Ubuntu without problems.
-- 
UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=unsubscribe

Re: Installation on PowerPC Mac running OS X 10.411

[Alexander Burger]

On Mon, Sep 14, 2009 at 11:43:31AM +0200, Henrik Sarvell wrote:
> ... just simply copied the picolisp executable that I had compiled in
> Ubuntu Feisty ... to a Mac and it simply ran it without any problems.

But Kyle has a PowerPC Mac. Does it emulate x86 instructions?
-- 
UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=unsubscribe

Re: Installation on PowerPC Mac running OS X 10.411

[Henrik Sarvell]

For what it's worth I think I once just simply copied the picolisp
executable that I had compiled in Ubuntu Feisty (observe no later
versions of Ubuntu will work as the GCC is broken on them) to a Mac
and it simply ran it without any problems.

/Henrik


On Mon, Sep 14, 2009 at 11:09 AM, Alexander Burger  wr=
ote:
> Hi Kyle,
>
> welcome to the mailing list!
>
>> I am having a bit of a problem installing picolisp on a PowerPC Mac
>> running OS X 10.411. =A0Here is the command line output after running th=
e
>> make command.
>
> I'm afraid I'm not of much help, as I don't have a Mac myself. I was
> hoping that some of the Mac users in this list would react :-(
>
>
>> PowerBook-12in:~/picoLisp-2.3.7/src kyle$ make picolisp
>> ...
>> make: gcc: Command not found
>
> This looks like you have no development environment installed. What
> needs to be done on a Mac to install or configure the C compiler?
>
>
> >From all what I've noticed about PicoLisp on the Mac so far, I believe
> it is a mess. The Mac obviously is not intended as a development
> machine. You have to fiddle arould with variables like
> MACOSX_DEPLOYMENT_TARGET (why doesn't the Mac find that out by itself?).
>
> Anyway, I hope that some of the Mac users could supply something
> helpful.
>
> Cheers,
> - Alex
> --
> UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=3dunsubscribe
>
-- 
UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=unsubscribe

Re: Installation on PowerPC Mac running OS X 10.411

[Alexander Burger]

Hi Kyle,

welcome to the mailing list!

> I am having a bit of a problem installing picolisp on a PowerPC Mac  
> running OS X 10.411.  Here is the command line output after running the 
> make command.

I'm afraid I'm not of much help, as I don't have a Mac myself. I was
hoping that some of the Mac users in this list would react :-(


> PowerBook-12in:~/picoLisp-2.3.7/src kyle$ make picolisp
> ...
> make: gcc: Command not found

This looks like you have no development environment installed. What
needs to be done on a Mac to install or configure the C compiler?


>From all what I've noticed about PicoLisp on the Mac so far, I believe
it is a mess. The Mac obviously is not intended as a development
machine. You have to fiddle arould with variables like
MACOSX_DEPLOYMENT_TARGET (why doesn't the Mac find that out by itself?).

Anyway, I hope that some of the Mac users could supply something
helpful.

Cheers,
- Alex
-- 
UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=unsubscribe