From: Matt <matt@excalamus.com>
To: "Ilya Konovalov" <aragaer@gmail.com>
Cc: "emacs-orgmode" <emacs-orgmode@gnu.org>
Subject: Re: [BUG] ":sep" header argument doesn't work in ob-shell [9.6.21 ( @ /home/aragaer/.config/emacs/elpa/org-9.6.21/)]
Date: Tue, 12 Mar 2024 11:22:28 +0100 [thread overview]
Message-ID: <18e322f5c04.c5668358256842.4107681299308039596@excalamus.com> (raw)
In-Reply-To: <87il1rn6fn.fsf@gmail.com>
---- On Tue, 12 Mar 2024 10:27:46 +0100 Ilya Konovalov wrote ---
>
> After some usage I found that this exact patch breaks
> `org-babel-import-elisp-from-file's own separator detection. It looks
> like it's better to leave it as `nil' unless specified.
Thanks for taking the time to look into it. According to my notes, :sep and :separator don't work for anything beyond basic table layout. I'm not familiar with org-table and there isn't much documentation on those keywords in the manual. The :sep keyword shows up for Texinfo and LaTeX. It looks like :sep is used for export? It's not clear to me how they're supposed to work with shell block output, or if that was even a consideration at all.
They were added in https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=a60a83fbb65a368bb96ea6aaf1db20706b3e99c5 claiming "better handling of table in shell scripts" So, it looks like their inclusion was intentional.
Maybe someone has deeper insights?
--
Matt Trzcinski
Emacs Org contributor (ob-shell)
Learn more about Org mode at https://orgmode.org
Support Org development at https://liberapay.com/org-mode
next prev parent reply other threads:[~2024-03-12 10:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-09 20:15 [BUG] ":sep" header argument doesn't work in ob-shell [9.6.21 ( @ /home/aragaer/.config/emacs/elpa/org-9.6.21/)] Ilya Konovalov
2024-03-12 9:27 ` Ilya Konovalov
2024-03-12 10:22 ` Matt [this message]
2024-03-12 10:41 ` Ilya Konovalov
2024-03-12 14:25 ` Ihor Radchenko
2024-03-12 14:38 ` 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=18e322f5c04.c5668358256842.4107681299308039596@excalamus.com \
--to=matt@excalamus.com \
--cc=aragaer@gmail.com \
--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).