emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Richard Stanton <rhstanton@berkeley.edu>
Cc: John Kitchin <jkitchin@andrew.cmu.edu>,  orgmode <emacs-orgmode@gnu.org>
Subject: Re: Trouble producing nicely aligned org tables from emacs-jupyter code blocks using latest org version
Date: Thu, 19 May 2022 21:37:54 +0800	[thread overview]
Message-ID: <87leux4p8t.fsf@localhost> (raw)
In-Reply-To: <09EF74F5-8C39-4773-9407-E65A46E2FE3B@berkeley.edu>

Richard Stanton <rhstanton@berkeley.edu> writes:

> A bit more experimenting shows that asynchronous execution is actually a part of my original problem. By default, I have jupyter-python blocks running asynchronously. In that case, the tables don’t format quite right, as I noted. But if I add the header ":async nil", the table comes out fine. Table formatting is OK in python blocks with or without asynchronous execution. 

Can you also see the problem without using jupyter-python?
A detailed recipe starting from emacs -Q would help (see


  reply	other threads:[~2022-05-19 13:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-18 20:05 Trouble producing nicely aligned org tables from emacs-jupyter code blocks using latest org version Richard Stanton
2022-05-18 20:16 ` John Kitchin
2022-05-18 20:56   ` Richard Stanton
2022-05-18 21:00     ` John Kitchin
2022-05-18 21:12       ` Richard Stanton
2022-05-19 13:37         ` Ihor Radchenko [this message]
2022-05-19 18:16           ` Richard H. Stanton
2022-05-19 19:22             ` Richard H. Stanton
2022-05-20  8:57               ` Ihor Radchenko
2022-05-22 13:05                 ` Richard Stanton
2022-05-26  4:27                   ` Ihor Radchenko
2022-05-26  8:42                     ` Richard Stanton
2022-05-19 23:22             ` Mark Barton

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=87leux4p8t.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=jkitchin@andrew.cmu.edu \
    --cc=rhstanton@berkeley.edu \


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