emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: "Berry, Charles" <ccberry@ucsd.edu>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Missing `Specific Header Arguments' in Manual
Date: Tue, 1 May 2018 23:05:58 +0000	[thread overview]
Message-ID: <9AB3025E-69D6-4971-989F-70A62695E470@ucsd.edu> (raw)
In-Reply-To: <87o9hzf3mu.fsf@nicolasgoaziou.fr>



> On May 1, 2018, at 2:49 PM, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
> 
> Hello,
> 
> "Berry, Charles" <ccberry@ucsd.edu> 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 manual.
> 
> 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 other.

Comparing `org-babel-common-header-args-w-values' to the info virtual index from 'Iheader arguments', I do not see  these header args in the manual and did not find them using `M-s o' in org-manual.org: 

cmdline (not in the previous info version either)

sep

tangle-mode

wrap

Also, `exports' is indexed as `@samp{export}'.

HTH,

Chuck

next prev parent reply	other threads:[~2018-05-01 23:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-01 21:34 Missing `Specific Header Arguments' in Manual Berry, Charles
2018-05-01 21:49 ` Nicolas Goaziou
2018-05-01 22:10   ` Kaushal Modi
2018-05-01 22:31     ` Berry, Charles
2018-05-02 12:47     ` Nicolas Goaziou
2018-05-08  8:29       ` Bastien
2018-05-08 14:05         ` Nicolas Goaziou
2018-05-08 16:01           ` Bastien
2018-05-08 16:28             ` Nicolas Goaziou
2018-05-01 23:05   ` Berry, Charles [this message]
2018-05-02 10:56     ` Nicolas Goaziou
2018-05-02 17:47       ` Berry, Charles
2018-05-08 23:47         ` Nicolas Goaziou

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=9AB3025E-69D6-4971-989F-70A62695E470@ucsd.edu \
    --to=ccberry@ucsd.edu \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    /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

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