emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>,
	"Berry, Charles" <ccberry@ucsd.edu>,
	Kaushal Modi <kaushal.modi@gmail.com>
Subject: Re: Missing `Specific Header Arguments' in Manual
Date: Tue, 08 May 2018 18:28:15 +0200	[thread overview]
Message-ID: <87tvriru1s.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87k1sedtmc.fsf@gnu.org> (Bastien's message of "Tue, 08 May 2018 18:01:15 +0200")

Bastien <bzg@gnu.org> 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
menu. IOW, there is no possible way to be confused with it when looking
for information about header arguments, because it is almost invisible.

You seem to be mixing the Org document and the ".info" file. Your
argument is:

  The natural expectation is for this section to list all header
  arguments

But this so-called section does not exist in the ".info" file. So the
expectation is wrong, at least from someone looking at the Info buffer,
which is the case we're talking about.

  reply	other threads:[~2018-05-08 16:28 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 [this message]
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=87tvriru1s.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=bzg@gnu.org \
    --cc=ccberry@ucsd.edu \
    --cc=emacs-orgmode@gnu.org \
    --cc=kaushal.modi@gmail.com \
    /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).