From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kaushal Modi Subject: Re: Missing `Specific Header Arguments' in Manual Date: Tue, 01 May 2018 22:10:48 +0000 Message-ID: References: <8D4BA262-9F3F-412B-8DF1-5F6A6E3E671C@ucsd.edu> <87o9hzf3mu.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000d32e01056b2c3eda" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:57452) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fDdUE-0005qh-JH for emacs-orgmode@gnu.org; Tue, 01 May 2018 18:11:03 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fDdUD-0004jo-7z for emacs-orgmode@gnu.org; Tue, 01 May 2018 18:11:02 -0400 Received: from mail-yb0-x22d.google.com ([2607:f8b0:4002:c09::22d]:34019) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fDdUD-0004jZ-2P for emacs-orgmode@gnu.org; Tue, 01 May 2018 18:11:01 -0400 Received: by mail-yb0-x22d.google.com with SMTP id b14-v6so4628041ybk.1 for ; Tue, 01 May 2018 15:11:01 -0700 (PDT) In-Reply-To: <87o9hzf3mu.fsf@nicolasgoaziou.fr> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Nicolas Goaziou Cc: emacs-orgmode , "Berry, Charles" --000000000000d32e01056b2c3eda Content-Type: text/plain; charset="UTF-8" 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 other. > 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. > 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. Kaushal -- Kaushal Modi --000000000000d32e01056b2c3eda Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Nicolas,

I ran into this issue too ve= ry 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.

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 th= is 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 search= ing, 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 th= at and found that node.
=C2=A0
=C2=A0You don't have to hunt them down. Within info, "i&= quot; then "header
argument". A half-decent completion mechanism will display all of them= .

Thanks for that tip! I guess I need t= o use the "i" approach more often than the plain old C-s. But I c= onfirm that with "i" followed by "header argument", it = presents a nice list of all arguments in the Ivy interface.

Kaushal
--

Kaus= hal Modi

--000000000000d32e01056b2c3eda--