From: "Berry, Charles" <ccberry@ucsd.edu>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>,
Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: Missing `Specific Header Arguments' in Manual
Date: Tue, 1 May 2018 22:31:23 +0000 [thread overview]
Message-ID: <7448EE3E-0FA0-468A-B37A-58E1941FFEBB@ucsd.edu> (raw)
In-Reply-To: <CAFyQvY1P1T4M4cLM6S8SoY4J1YTqGoiD4HsL2-hphxZAAu0hLg@mail.gmail.com>
> On May 1, 2018, at 3:10 PM, Kaushal Modi <kaushal.modi@gmail.com> 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 <mail@nicolasgoaziou.fr> 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 other.
I should have said `Thanks!' for that.
>
> 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. So searching is not consistent any more.
>
> I was able to do this earlier.. open Org Info manual, C-s :eval, keep on C-s as it found *all hits* in the manual. Now in 9.2, the only hits are in (org) Exporting Code Blocks, which is not very useful.
>
> Can we prefix all the header arg references in the manual with ":" so that while searching, I can easily find the (org) Evaluating Code Blocks node? I was having trouble finding this node as "eval" is too generic of a string.. thankfully I remembered the "never-export" value, searched for that and found that node.
>
> You don't have to hunt them down. Within info, "i" then "header
> argument". A half-decent completion mechanism will display all of them.
>
I guess I don't have a half-decent completion mechanism - just ido. But this got me looking at info, which I do not know well enough.
It turns out that (upper case) `I' followed by `header argument' followed by RET pops up an `Info Virtual Index' which is what I wanted.
And this works even without any completion add-ons.
> Thanks for that tip! I guess I need to use the "i" approach more often than the plain old C-s. But I confirm that with "i" followed by "header argument", it presents a nice list of all arguments in the Ivy interface.
Yes. This expands my `info fu'. So thanks again.
Chuck
next prev parent reply other threads:[~2018-05-01 22:31 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 [this message]
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=7448EE3E-0FA0-468A-B37A-58E1941FFEBB@ucsd.edu \
--to=ccberry@ucsd.edu \
--cc=emacs-orgmode@gnu.org \
--cc=kaushal.modi@gmail.com \
--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
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).