Ilya Konovalov writes:
> On current master using ":sep" header argument does not work as
> expected and records are always split on whitespaces. For example:
>
> #+begin_src sh :sep "\t"
> echo hello world
> echo test
> #+end_src
>
> #+RESULTS:
> | hello | world |
> | test | |
It
Matt writes:
> ... 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
>
I assumed that https://org-babel.readthedocs.io/ is at least somewhat
related to org documentation. Looks like I was wrong.
The :separator parameter seems to be related to how block's :var
arguments are formatted when passing to the shell script.
In most cases separator is not passed to
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
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.
Ilya Konovalov writes:
> On current master using ":sep" header argument does not work as
> expected and records
On current master using ":sep" header argument does not work as
expected and records are always split on whitespaces. For example:
#+begin_src sh :sep "\t"
echo hello world
echo test
#+end_src
#+RESULTS:
| hello | world |
| test | |
It looks like the issue is in the
