From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Alain.Cochard@unistra.fr
Cc: emacs-orgmode@gnu.org
Subject: Re: "COMMENT" keyword not properly documented in the manual
Date: Sat, 14 Jan 2017 00:28:02 +0100 [thread overview]
Message-ID: <87ziiuzgjh.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <22644.36612.316302.470247@frac.u-strasbg.fr> (Alain Cochard's message of "Tue, 10 Jan 2017 08:36:36 +0100")
Hello,
Alain.Cochard@unistra.fr writes:
> But unless the use of this variable is obsolete, I feel it has to be
> documented -- could be as discreet as one sentence in a footnote.
> Otherwise, with a nil default, even people using the export features
> would have difficulties to know about it.
I dropped a note about in "agenda views" part of the manual.
>
> (More generally, what would be the harm of having some appendix with a
> list of all customizable variables? Seems to me it could help
> beginners to learn Org; sure, there is 'C-h v org-<TAB>', but it's not
> exactly the same for me.)
There is a lot of variables. We cannot possibly document all of them in
the manual. However, the best way for a beginnier to discover these
options is probably to call "M-x customize-group RET org RET".
Regards,
--
Nicolas Goaziou 0x80A93738
next prev parent reply other threads:[~2017-01-13 23:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 16:31 "COMMENT" keyword not properly documented in the manual Alain.Cochard
2017-01-08 23:51 ` Nicolas Goaziou
2017-01-10 7:36 ` Alain.Cochard
2017-01-10 18:05 ` Samuel Wales
2017-01-13 23:28 ` Nicolas Goaziou [this message]
2017-01-10 20:10 ` Matt Price
2017-06-06 15:19 ` multiple agenda views -- sticky agendas?, buffer renaming? Alain.Cochard
2017-07-03 5:09 ` Bastien
2017-08-22 13:25 ` Alain.Cochard
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=87ziiuzgjh.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=Alain.Cochard@unistra.fr \
--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).