emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: Colin Baxter <m43cap@yandex.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: bash babel code gives error
Date: Sat, 29 Aug 2020 09:55:38 -0400	[thread overview]
Message-ID: <87h7slsgit.fsf@kyleam.com> (raw)
In-Reply-To: <87y2m3m1xs.fsf@yandex.com>

Colin Baxter writes:

>>>>>> Colin Baxter <m43cap@yandex.com> writes:
>     > Hello, I have various .tex files and an org file in the same
>     > directory. In the org file is the following simple bash babel-code
>     > #+begin_src bash sha256sum *.tex > CHECKSUM #+end_src
>     > This code block used to work but no longer.
> This is not wholly correct. It does indeed produce a checksum file
> CHECKSUM, but gives the "Error reading results:
> (beginning-of-buffer)". No such error was called in the past (~ a month or
> so ago).

Thanks for reporting.  The _display_ of this warning starts with my
14878f3f9 (ob-core: Display warning on failure to read results,
2020-05-21).  Here's the associated thread on the mailing list:

On that commit's parent (eecee2266), the error is triggered and caught
in the same way, but "Error reading results: (beginning-of-buffer)" is
buried in the messages buffer rather than being displayed as a warning.

I'll need to take a closer look at what's going on, though I wouldn't be
surprised if it's been around for a long time.

  reply	other threads:[~2020-08-29 13:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-25 10:36 bash babel code gives error Colin Baxter
2020-08-25 10:53 ` Colin Baxter
2020-08-29 13:55   ` Kyle Meyer [this message]
2020-08-29 17:22     ` [PATCH] ob-core: Avoid table conversion warning for empty results Kyle Meyer
2020-08-29 19:53       ` Colin Baxter
2020-08-30  6:53         ` Colin Baxter
2020-09-01  4:04           ` Kyle Meyer

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:

  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=87h7slsgit.fsf@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=m43cap@yandex.com \


* 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


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).