From: gerard.vermeulen@posteo.net
To: Nathan Van Ymeren <n@0x85.org>
Cc: emacs-orgmode@gnu.org,
emacs-orgmode-bounces+gerard.vermeulen=posteo.net@gnu.org
Subject: Re: Slashes inserted into Common Lisp code evaluation results
Date: Wed, 03 May 2023 07:14:03 +0000 [thread overview]
Message-ID: <68906e4d3e43b34d22eb3f7484ec492b@posteo.net> (raw)
In-Reply-To: <3C591572-A5CB-494F-BD87-7DCE89B9C855@0x85.org>
Igor, merged the patch yesterday with the bugfix branch.
It is now in https://elpa.gnu.org/devel/org-9.7pre0.20230502.124756.tar
or later.
It should not matter whether you are using Emacs-28 or Emacs-29.
Regards -- Gerard
On 03.05.2023 08:00, Nathan Van Ymeren wrote:
> Ahh, I forgot to specify. I too use Sly in lieu of Slime, though I'm
> on emacs 28. That patch does not appear to have made its way into the
> prerelease I’m running. I will apply it manually later this evening
> and see how it goes.
>
> Thanks,
>
> N
>
> May 2, 2023 03:52:52 gerard.vermeulen@posteo.net:
>
>>
>>
>> On 02.05.2023 08:18, Nathan Van Ymeren wrote:
>>> When I specify double width floats, they appear with slashes embedded
>>> in the RESULTS blocks, like so:
>>> #+begin_src lisp
>>> (+ 1 0.0002d0)
>>> #+end_src
>>> #+RESULTS:
>>> : 1\.0002d0
>> [...]
>>> Is this a bug? If not, how do I suppress this behaviour?
>>>
>> Do you use SLIME?
>> I use SLY on a recent emacs-29.0.90 build with a recent org-9.7pre.
>> My result is (without the escaped dot):
>>
>> #+begin_src lisp
>> (+ 1 0.0002d0)
>> #+end_src
>>
>> #+RESULTS:
>> : 1.0002d0
>>
>> But I needed also to patch ob-lisp, see:
>> https://list.orgmode.org/480536eb12bf49144384f4b1a85d8bdf@posteo.net/
>>
>> In my opinion, SLY is friendlier out of the box than SLIME.
>>
>> Regards -- Gerard
next prev parent reply other threads:[~2023-05-03 7:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-02 6:18 Slashes inserted into Common Lisp code evaluation results Nathan Van Ymeren
2023-05-02 10:52 ` gerard.vermeulen
2023-05-03 6:00 ` Nathan Van Ymeren
2023-05-03 7:14 ` gerard.vermeulen [this message]
2023-05-03 7:45 ` Ihor Radchenko
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=68906e4d3e43b34d22eb3f7484ec492b@posteo.net \
--to=gerard.vermeulen@posteo.net \
--cc=emacs-orgmode-bounces+gerard.vermeulen=posteo.net@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=n@0x85.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).