Hello Alexis :-)
You are now subscribed
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
e 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
;)
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
ed 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
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
n; 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
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?
A
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/), whi
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,
xecutable:
(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." )
nality 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
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
+-+-+ | car | cdr | +-+-+
which, in an English-language left-to-right document, is what i
would expect.
Is there a particular reason for the former?
Alexis.
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
at the higher.
The important point is that the pointer *TO* a PicoLisp item may
point to different parts of the cell:
Ah, okay, now i understand.
Confusing?
No, i found your explanation succinct and clear - thank you!
Alexis.
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject
Amaury Hernández Águila writes:
Any suggestions to the name of the library? PicoML sounds good.
i would suggest not using 'PicoML' - that sounds like a dialect of
the ML programming language:
https://en.wikipedia.org/wiki/ML_%28programming_language%29
Alexis.
--
U
mode,
not the mode available on MELPA, i.e. the former is loaded and
shadowing the latter.
Alexis.
[1] For a discussion on why my package on MELPA still has the same
name as the one bundled with PicoLisp,
cf. https://github.com/milkypostman/melpa/issues/2514.
--
UNSUBSCRIBE: mailto:pico
and it might
be difficult for people familiar with either package to help you
untangle what's going on.
Alexis.
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
comes that users start saying that picolisp-mode
on MELPA should be the official version then lets cross that
road when we get there.
If people here would now like me to rename my mode, i'd be happy
to initiate that process.
Alexis.
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?su
d wanted me to
remove my mode from MELPA - or at least, rename it - in order to
avoid confusion, i'd be fine with that as well. :-)
Alexis.
[1] Yes, i'm aware of the claim that "[i]f you think paredit is
not for you then you need to become the kind of person that
paredit
mment-499743025
Also, did you end up resolving the issue you raised about calling
`picolisp-repl`? i don't appear to have received any response from
you to my last query:
https://github.com/flexibeast/picolisp-mode/issues/2#issuecomment-478310047
Alexis.
--
UNSUBSCRIBE: mailto:picolisp@softw
somewhere ?
It's currently not a defcustom, but i'll change that asap
(hopefully in the next 24 hours or so). In the meantime, though,
you can add `(setq inferior-plisp--command-line " +")` to
your Emacs config.
Alexis.
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Jean-Christophe Helary
writes:
Thank you Alexis, and sorry to bother you about that. It was
late but it's something I could have checked myself.
It's no problem! As it was marked as an internal variable, it's
good to err on the side of not trying to mess with it
extern
is that Tomas is using the latter meaning, and wants
'pure' functions that simply return strings, without sending them
to an output device. The final string to be output would be
created by combining the return values of multiple functions,
possibly performing transformations on th
Good bye Alexis :-(
You are now unsubscribed
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
24 matches
Mail list logo
