From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vladimir Nikishkin 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: Tue, 22 Oct 2019 09:35:56 +0800 Message-ID: References: <87h842kfgi.fsf@delllaptop.lockywolf.net> <80649399-906c-76fd-dd0e-2040fd62f9de@gmail.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="------------76AB245F5D847E7B8F9BA90B" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:39162) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iMj5i-0002HC-7i for emacs-orgmode@gnu.org; Mon, 21 Oct 2019 21:36:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iMj5h-0002mA-1Z for emacs-orgmode@gnu.org; Mon, 21 Oct 2019 21:36:06 -0400 Received: from mail-wr1-x444.google.com ([2a00:1450:4864:20::444]:45569) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iMj5g-0002ld-OK for emacs-orgmode@gnu.org; Mon, 21 Oct 2019 21:36:04 -0400 Received: by mail-wr1-x444.google.com with SMTP id q13so11034483wrs.12 for ; Mon, 21 Oct 2019 18:36:04 -0700 (PDT) In-Reply-To: <80649399-906c-76fd-dd0e-2040fd62f9de@gmail.com> Content-Language: en-US List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Neil Jerram , emacs-orgmode@gnu.org This is a multi-part message in MIME format. --------------76AB245F5D847E7B8F9BA90B Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 21/10/2019 23:24, Vladimir Nikishkin wrote: > Well, checking for "output" doesn't seem to be useful any way, since > "output" is never 'nil. >=20 > Regarding the fact that the error should be reported to the geiser > mailing list, that's entirely true. The problem is that the person who > would be responsible for this error would be me. :) At least for the > chibi-scheme part. >=20 > I don't think that having a few extra checks on the org/geiser interfac= e > is bad, especially there is also comint coming into play. I can imagine= > valid reasons when "output" is not a valid serialized scheme expression= =2E >=20 > On 21/10/2019 22:46, Neil Jerram wrote: >> On Mon, 21 Oct 2019 at 15:16, Vladimir Nikishkin > > 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 schem= e >> interpreter, and is expected to be formatted specifically to be fe= d 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 so= me >> 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 'n= il, >> but there is no check for it. >> >> So, again, both of the geiser steps (namely, (a) serializing a sex= p in >> scheme, and (b) de-serializing it in geiser-eval--retort-output) m= ay >> 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.=C2=A0 (I'm guilty of doi= ng that >> in the past too!) >> >> Do you have a specific example of that?=C2=A0 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. >> =C2=A0=C2=A0 >> >> >> Yes, I have seen this going on, actually quite a lot, because both= >> geiser and different scheme interpreters are in constant developme= nt 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. >> =C2=A0 >> Best wishes, >> =C2=A0 =C2=A0 =C2=A0Neil >> =C2=A0 A particularl example could be, perhaps, when an interpreter crashes and produces something like "Segmentation fault", which is not a valid geiser-sexp. --------------76AB245F5D847E7B8F9BA90B Content-Type: application/pgp-keys; name="pEpkey.asc" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="pEpkey.asc" -----BEGIN PGP PUBLIC KEY BLOCK----- mQENBFyI+EABCADEcLowMLOf6mUPlBOD66CUc2RSNNy0AJJoONowHiAu5buWdrhK vXvIeI+wIkZS3DrzK2EDQlTZKr3UIGMiyNBT2O+bCr3+9jH7uyAr/qjSpy5sbkiT AxcI40mAZ7yY14iRObNaJmLT89bPJI60/qANxeOjI75z0l3JjsI2/uxkzzzaws8o hQELOoWTZQkuiNdwcpFsw65r8/xzu65PdrzaP3/EwWVEb5ggWQm6MmVe86XJaRrH VJ4ZmJx14GoQ0uak9bty8XJ22HJxplSrR5PGy8N9IPUkUrMJhqI4g7j2Ssm4NeRy m/xDryJozSLeWBR1MH6isxZ4GvuUmu5iSxD7ABEBAAG0KFZsYWRpbWlyIE5pa2lz aGtpbiA8bG9ja3l3b2xmQGdtYWlsLmNvbT6JAVQEEwEIAD4WIQRQ7nw05Jjmw747 p2MEnyvRK/AE6QUCXIj4QQIbAwUJAeEzgAULCQgHAgYVCgkICwIEFgIDAQIeAQIX gAAKCRAEnyvRK/AE6WemB/46op9q3nlKFZKVgLPzT496wz8XGGd2gSf7BCh6rwj9 jpCVf3fNTuHjBTNgQvlkGnGQjOXcJWxgjDa248pPv8Ofq7HkUYa2TviNluYCYuSP TBspAvD+988hlhLX/pmgpdJdzNFYGhxK1kaWTDeVoEf5/68bc2AknQkqEG2iadYo CL8ENIBjw/3xLCG5MbEBiwlHwa+m1nCqbLcIUb6IX1kx4oP2J5hUPtjzyg9XKLRY 5hfl2w0JkxU6rayZb7Vjrpx1Bfx7f5mJH4Km9E2NrpsBaU6l+6IgWp8zhgtvyED0 nzimOmzCVAtJ5rxEEBI9MwXY8QFjTsVM0SSWPip36Y2DuQENBFyI+EABCACVphlz Sw9ANVHwol/zU6CIGIgpunGHyFYguNjEnoyGNl5lXuPeUBHzyvrH2U0D5s3lNqTD dSAaJcuhhVkUz0iHQJ1C9Qf2a50bGBVSTcZv2R42YDD8LGZNSXmDpPEF5kO3dWhN zG5O7Ncz6RdiMDutNAbUdOGEbz/WSacxzTD64JRc3QFzmNHSodGYVX1qqARjMjaa MzP20m4k4a3fGrlw5XzsokSP8UwN733+osYoGEoXOXG0EtwSQXFrSSeS8oS7uOkY F5FBugRyHUHHndCEaE0BcH+TdGORntSCyIY0EA5+HvMUVcVCom5dnlum6QgCGmiy guZpbgqqFuzFyUBlABEBAAGJATwEGAEIACYWIQRQ7nw05Jjmw747p2MEnyvRK/AE 6QUCXIj4QAIbDAUJAeEzgAAKCRAEnyvRK/AE6Q8MCADB+fRtDftYHPWggeGpIV93 vxR6bkLrBSG9OYttK3yg8dk/FpFQ3U8nRavJPvlYyPMdwcOhwHBxrCKWWz5CmPNL WeoboRGWcsWd99Qd34O587pAtuWecm7jOQhPfptJqKbFSfnXzPMGD+2N86mW6uJq swMP1Nf1bUYBlh3udGB3hJCGCt2kQ4dVXCPI75IIrHR4KsUSRkSwXWjqIBbQkQN1 Rbxqo1jwLfGsjc65e+g61tr06aEthQTRfyLkA6k2YMIdExiqovDrOH24oS7qkCcq D01kCeCgeyg89qaBE0WEbJRxELq5LR5rxPuDs5zwMp2RjQ5TB+ik/5IGIyUuadRK =3DvJFI -----END PGP PUBLIC KEY BLOCK----- --------------76AB245F5D847E7B8F9BA90B--