From: Neil Jerram <neiljerram@gmail.com>
To: Vladimir Nikishkin <lockywolf@gmail.com>,
Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: Bug: Problems with ob-scheme in geiser-eval--retort-output [9.2.6 (9.2.6-4-ge30905-elpa @ /home/lockywolf/.emacs.d/elpa/org-20191021/)]
Date: Mon, 21 Oct 2019 15:46:49 +0100 [thread overview]
Message-ID: <CAKuG=vsiaxWHAGk1L-jFUG2xsyABtFsccC2pYM+p2qbYd1uSmQ@mail.gmail.com> (raw)
In-Reply-To: <c62d8deb-1ef7-378a-60f5-b7775f34a6d5@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1549 bytes --]
On Mon, 21 Oct 2019 at 15:16, Vladimir Nikishkin <lockywolf@gmail.com>
wrote:
> Yeah. The "output" is not the result of geiser's elisp functions, as far
> as I understand, it comes from comint, which reads it from a scheme
> interpreter, and is expected to be formatted specifically to be fed into
> geiser-eval--retort-output by the geiser scheme functions (running
> inside a scheme interpreter).
>
> So "output" is never 'nil, because comint, when scheme produces some
> rubbish, just makes it an empty string, which is not 'nil.
>
> Then, "output" is expected to be "retorted" back from a serialized
> scheme expression into an elisp expression by
> geiser-eval--retort-output. And this actually may and produce a 'nil,
> but there is no check for it.
>
> So, again, both of the geiser steps (namely, (a) serializing a sexp in
> scheme, and (b) de-serializing it in geiser-eval--retort-output) may fail.
>
I agree that it's fragile for geiser/scheme to output a sexp that it hopes
geiser/elisp will be able to read back. (I'm guilty of doing that in the
past too!)
Do you have a specific example of that? It feels like the right thing to
do would be to report that to the Geiser list, as this could and should be
fixed entirely within the Geiser code.
>
> Yes, I have seen this going on, actually quite a lot, because both
> geiser and different scheme interpreters are in constant development and
> get broken every other day.
>
I use Org with Guile 2.2.3 (via Geiser), and it seems a pretty stable setup
to me.
Best wishes,
Neil
[-- Attachment #2: Type: text/html, Size: 2198 bytes --]
next prev parent reply other threads:[~2019-10-21 14:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 2:19 Bug: Problems with ob-scheme in geiser-eval--retort-output [9.2.6 (9.2.6-4-ge30905-elpa @ /home/lockywolf/.emacs.d/elpa/org-20191021/)] Vladimir Nikishkin
2019-10-21 10:42 ` Neil Jerram
[not found] ` <c62d8deb-1ef7-378a-60f5-b7775f34a6d5@gmail.com>
2019-10-21 14:46 ` Neil Jerram [this message]
[not found] ` <80649399-906c-76fd-dd0e-2040fd62f9de@gmail.com>
2019-10-22 1:35 ` Vladimir Nikishkin
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='CAKuG=vsiaxWHAGk1L-jFUG2xsyABtFsccC2pYM+p2qbYd1uSmQ@mail.gmail.com' \
--to=neiljerram@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=lockywolf@gmail.com \
/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).