From: "Nicholas Savage" <nick@nicksavage.ca>
To: "Emanuel Berg via General discussions about Org-mode."
<emacs-orgmode@gnu.org>
Subject: Re: babel output seems to drop anything before % (in session)
Date: Thu, 06 May 2021 07:39:25 -0400 [thread overview]
Message-ID: <f01c0d68-6bd5-4337-b14b-0bfe83013c64@www.fastmail.com> (raw)
In-Reply-To: <CAFLB-+ZXO8NnN_d=wDY+TZw64LWOo3Wdp37x=t46EbwUCVSfVw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1622 bytes --]
I can confirm this too on the latest master.
I took a quick peek this morning, and my suspicion is that the problem is somewhere within org-babel-comint-with-output in lisp/ob-comint.el, but I'm not positive at this point.
On Wed, May 5, 2021, at 22:35, John Corless wrote:
> Confirmed
>
> Daniele,
>
> I was able to reproduce the behavior you described. Using the test case...
>
> #+BEGIN_SRC shell script :results output
> ping -c 1 127.0.0.1
> #+END_SRC
>
> ... the results output matches what I get in a bash shell. But if you add the :session to the header args like this...
>
> #+BEGIN_SRC shell script :results output :session test
> ping -c 1 127.0.0.1
> #+END_SRC
>
> ... the output line that includes "0% packet loss" gets truncated to after the "%" sign.
>
> I tested with 9.4.5.
>
> John
>
>
> On Wed, May 5, 2021 at 10:19 AM Daniele Pizzolli <dan@toel.it> wrote:
>>
>> Hello,
>>
>> Try to execute a few times the following and see the output corrupted in
>> the line:
>>
>> #+BEGIN_EXAMPLE
>> 1 packets transmitted, 1 received, 0% packet loss, time 0ms
>> #+END_EXAMPLE
>>
>> #+PROPERTY: header-args:shell
>> #+PROPERTY: header-args:shell+ :results output verbatim :wrap src text :session test
>>
>> #+NAME: ping
>> #+BEGIN_SRC shell
>> ping -c 1 127.0.0.1
>> #+END_SRC
>>
>> I tried to write a test (now with the :expected-result :failed), that
>> hit the problem both in main and master (applies fine to both).
>>
>> I was not able to fix it, but hopefully the tests are still useful for
>> somebody more knowledgeable!
>>
>> Thanks for you suggestion/fix!
>>
>> Best,
>> Daniele
>>
[-- Attachment #2: Type: text/html, Size: 3965 bytes --]
next prev parent reply other threads:[~2021-05-06 11:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-05 15:15 babel output seems to drop anything before % (in session) Daniele Pizzolli
2021-05-06 2:35 ` John Corless
2021-05-06 11:39 ` Nicholas Savage [this message]
2021-05-06 12:24 ` Ihor Radchenko
2021-05-06 23:44 ` Nick Savage
2021-05-15 20:47 ` Bastien
2021-06-09 3:41 ` Kaushal Modi
2021-06-09 3:54 ` Kaushal Modi
2021-06-09 4:01 ` Kaushal Modi
2021-11-09 21:21 ` Kaushal Modi
2021-11-10 4:13 ` Ihor Radchenko
2022-06-07 0:01 ` Felix Freeman via General discussions about Org-mode.
2022-06-07 21:50 ` Felix Freeman via General discussions about Org-mode.
2022-06-07 22:55 ` Felix Freeman via General discussions about Org-mode.
2022-06-18 3:20 ` [PATCH] " Ihor Radchenko
2022-08-26 12:51 ` Ihor Radchenko
2022-09-25 1:44 ` Ihor Radchenko
2022-09-25 2:02 ` Bastien Guerry
2022-07-16 10:04 ` 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=f01c0d68-6bd5-4337-b14b-0bfe83013c64@www.fastmail.com \
--to=nick@nicksavage.ca \
--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).