From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: "Berry, Charles" <ccberry@ucsd.edu>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Missing `Specific Header Arguments' in Manual
Date: Tue, 01 May 2018 23:49:13 +0200 [thread overview]
Message-ID: <87o9hzf3mu.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <8D4BA262-9F3F-412B-8DF1-5F6A6E3E671C@ucsd.edu> (Charles Berry's message of "Tue, 1 May 2018 21:34:50 +0000")
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.
> Is there any way to recover this?
>
> Or maybe add an appendix just for specific header args rather than
> having to hunt them down in the Main Appendix?
You don't have to hunt them down. Within info, "i" then "header
argument". A half-decent completion mechanism will display all of them.
In the worse case, i.e., you have no decent completion mechanism, you
can go to the Main Index then "C-s header argument M-s o".
Now they are sorted, you can also search by topic. For example, if you
know the specific header argument your are looking after is related to
tangling, you can go directly to (info "(org) Extracting Source Code").
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2018-05-01 21:49 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 [this message]
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
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=87o9hzf3mu.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=ccberry@ucsd.edu \
--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).