Hello,
"Berry, Charles" writes:
> @cindex @code{:sep}, src header argument
>
> The @code{:sep} header argument is the delimiter for saving results as tables
> to files (@pxref{file}) external to Org mode. Org defaults to tab delimited
> output. The function, @code{org-open-at-point}, which is
Bastien writes:
> See line 17450 in doc/org-manual.org of the current master.
This is not a section, actually not in the Texinfo sense. See line 17452
in the same document. I.e., there is no node attached to it, it cannot
be accessed from "m" menu from `info', and it doesn't appear in the node
m
Hi Nicolas,
Nicolas Goaziou writes:
>> There is a section called "Header arguments" in the new
>> org-manual.org.
>
> No, there is not.
See line 17450 in doc/org-manual.org of the current master.
--
Bastien
Hello,
Bastien writes:
> Why did you remove colon prefixes?
As I explained, many structural objects start with a colon. Some of them
were indexed with a colon, others were not. This is confusing. The best
solution was to remove colons from entries in index. Adding colons
everywhere would crippl
Hi Nicolas,
Nicolas Goaziou writes:
> Kaushal Modi writes:
>
>> In the Org 9.1 version manual, it was possible to search ":eval" and find
>> what I was looking for. In 9.2 manual, very few of the header arguments are
>> documented with the colon prefix.
>
> I removed all colon prefixes, so it i
> On May 2, 2018, at 3:56 AM, Nicolas Goaziou wrote:
>
> Hello,
>
> "Berry, Charles" writes:
>
>> cmdline (not in the previous info version either)
>> sep
>
> I'm not sure what these two are about (the :sep is not documented
> either).
Re :sep, FWIW I found this in org.texi from late 2017:
Hello,
Kaushal Modi writes:
> In the Org 9.1 version manual, it was possible to search ":eval" and find
> what I was looking for. In 9.2 manual, very few of the header arguments are
> documented with the colon prefix.
I removed all colon prefixes, so it is a bug if any header argument is
prefix
Hello,
"Berry, Charles" writes:
> cmdline (not in the previous info version either)
> sep
I'm not sure what these two are about (the :sep is not documented
either).
Besides, :cmdline doesn't seem to be used consistently everywhere. It
could probably be moved out of "ob-core.el" and re-introduc
> On May 1, 2018, at 2:49 PM, Nicolas Goaziou wrote:
>
> Hello,
>
> "Berry, Charles" writes:
>
>> I miss not being able to refer to a single section in the manual so
>> I can browse the useful babel header arguments whose name, spelling,
>> or function I have forgotten. I guess it was re-org
> On May 1, 2018, at 3:10 PM, Kaushal Modi wrote:
>
> Hi Nicolas,
>
> I ran into this issue too very recently when I wanted to search for ":eval".
> Details below.
>
> On Tue, May 1, 2018 at 5:50 PM Nicolas Goaziou wrote:
>
> Yes, and it took me a long while to properly put all these argum
Hi Nicolas,
I ran into this issue too very recently when I wanted to search for
":eval". Details below.
On Tue, May 1, 2018 at 5:50 PM Nicolas Goaziou
wrote:
>
> Yes, and it took me a long while to properly put all these arguments in
> a logical place instead of having them piled on top of each
Hello,
"Berry, Charles" writes:
> I miss not being able to refer to a single section in the manual so
> I can browse the useful babel header arguments whose name, spelling,
> or function I have forgotten. I guess it was re-organized out of the
> manual in the update to the new org formatted manu
I miss not being able to refer to a single section in the manual so I can
browse the useful babel header arguments whose name, spelling, or function I
have forgotten. I guess it was re-organized out of the manual in the update to
the new org formatted manual.
Is there any way to recover this?
13 matches
Mail list logo
