From: Lawrence Bottorff <borgauf@gmail.com>
To: emacs-orgmode Mailinglist <emacs-orgmode@gnu.org>
Subject: Exploring picolisp
Date: Sun, 25 Feb 2018 20:29:21 -0500 [thread overview]
Message-ID: <CAFAhFSWYj33vfz=+dYyXKQOm3rez4hoO0Hmkx_iQ-sPyR_v2iw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1275 bytes --]
I'm looking at picolisp -- and wondering how it works, or better, why it
doesn't really work work with babel. First problem, I couldn't get any form
of picolisp to work in Emacs -- until I stopped starting Emacs with
emacsclient -c -a ''
which sets up my daemon first. Got abstruse error -- and it creates a file
called `editor-orig` in `~/.pil` which blocks any further attempts. After
tearing stuff out of my init diaspora for hours, I finally found that a
straight
>emacs &
made picolisp-mode work, otherwise, not. Very weird. But then I see this
<https://github.com/tj64/ob-picolisp> and, yes, picolisp babel seems to
work for all the examples. However, a regular function declaration
#+name: hello
#+begin_src picolisp
(de hello (X)
(prinl "Hello " X) )
#+end_src
-- goes nowhere. But then C-c C-c in a picolisp code block isn't firing up
a REPL, so where can it go? Nowhere. Lisp, Scheme & Cie. all require a
running REPL that org-mode knows about. And if I just bring up
picolisp-mode with a picolisp file and fire up a REPL, that REPL doesn't
know anything about my org-mode picolisp code blocks.
I don't mean to complain or sound negative, but picolisp as is can't really
be included as a babel language, can it? Maybe it worked once, but doesn't
now?
LB
[-- Attachment #2: Type: text/html, Size: 1621 bytes --]
next reply other threads:[~2018-02-26 1:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-26 1:29 Lawrence Bottorff [this message]
2018-03-03 14:34 ` Exploring picolisp Thorsten Jolitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAFAhFSWYj33vfz=+dYyXKQOm3rez4hoO0Hmkx_iQ-sPyR_v2iw@mail.gmail.com' \
--to=borgauf@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).