From: Alain.Cochard@unistra.fr
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode@gnu.org, Alain.Cochard@unistra.fr
Subject: Re: Confused about the explanation for 'org-cycle'
Date: Thu, 28 Sep 2017 23:04:57 +0200 [thread overview]
Message-ID: <22989.25593.198323.807112@frac.u-strasbg.fr> (raw)
In-Reply-To: <87h8vmopww.fsf@nicolasgoaziou.fr>
Thanks for your answer.
Nicolas Goaziou writes on Thu 28 Sep 2017 16:31:
> > More generally, I cannot remember the number of times when I read
> > the manual, do not understand it,
>
> This is exactly where the manual fails. What is the point of an
> exhaustive, yet not understandable, manual?
It looks like I did not make myself clear (or I don't understand your
sentence above): the "number of times" to which I was referring are
when the manual is /not exhaustive enough/ (to me, that is).
> > for the (admittedly not very smart) beginner that I am, and I
> > would favor completeness -- with footnotes, dumb examples to get
> > started, more cross-references, even repetitions -- over clarity.
>
> Completeness is not possible. For example, we do not document every
> variable in the manual. Besides, when reading a pile of special
> rules for special cases, the reader may lose focus and miss the
> whole concept.
I guess the degree of expected completeness varies between
individuals... This being said, I contend that it is often possible
to add a lot of completeness mostly without altering clarity, using an
appropriate organization (like more in-depth sections or examples
sections). (In fact, it seems to me that this is what is already
often done.)
Precisely, regarding variable documentation, I remember that you
already made your point in an earlier email, advocating the use of
customize-group; while I certainly do not argue about its usefulness
for some purposes, for me it is often much less convenient than
exhaustive variable documentation would be.
I have a fresh example in mind to illustrate my point: this afternoon,
I was looking for org-blank-before-new-entry. I vaguely remembered it
existed and was searching the manual (from Info) with the regexps
'blank' and 'list'. Had the variable been mentioned, I would have
found it within seconds; by contrast I can't imagine how much time I
would need using customize-group... And, in this case, I don't see
how having a separate section (e.g., an appendix, much like the
Variable section), with all variables documented, would remove the
least bit of clarity.
Also, I am aware that there exist at the Worg site many tutorials
which give more in-depth documentation on specific topics. Those
tutorials are great in general. Nevertheless, I often observe that,
by contrast with the manual which is meant to be up-to-date, they are
obsolete in some respect, which makes them difficult for me to use in
order to get started.
> BTW, a "docstring" is the documentation you get when using, e.g.,
> `C-h v' or `C-h f'.
Thank you. In retrospect, I realize I should have looked it up
myself...
Regards,
a.
--
EOST (École et Observatoire des Sciences de la Terre)
IPG (Institut de Physique du Globe) | alain.cochard@unistra.fr
5 rue René Descartes [bureau 106] | Phone: +33 (0)3 68 85 50 44
F-67084 Strasbourg Cedex, France | Fax: +33 (0)3 68 85 01 25
next prev parent reply other threads:[~2017-09-28 21:05 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-18 14:04 Confused about the explanation for 'org-cycle' Alain.Cochard
2017-09-19 5:08 ` Matt Lundin
2017-09-20 10:57 ` Nicolas Goaziou
2017-09-26 8:54 ` Alain.Cochard
2017-09-26 10:41 ` Nicolas Goaziou
2017-09-26 12:48 ` Alain.Cochard
2017-09-28 13:44 ` org-list-empty-line-terminates-plain-lists removed but still mentioned in the manual Alain.Cochard
2017-09-28 14:07 ` Nicolas Goaziou
2017-09-28 14:31 ` Confused about the explanation for 'org-cycle' Nicolas Goaziou
2017-09-28 15:29 ` Robert Horn
2017-09-28 16:10 ` Kyle Meyer
2017-09-28 16:17 ` Eric S Fraga
2017-09-28 21:04 ` Alain.Cochard [this message]
2017-09-28 21:22 ` Josiah Schwab
2017-09-28 21:30 ` Nicolas Goaziou
2017-10-05 8:17 ` Alain.Cochard
2017-11-10 17:23 ` How to use case sensitive org-search-view? Alain.Cochard
2017-11-14 14:26 ` Matt Lundin
2017-11-14 15:30 ` Alain.Cochard
2017-11-14 20:35 ` Nicolas Goaziou
2017-11-14 20:55 ` Tim Cross
2017-11-15 14:02 ` Nicolas Goaziou
2017-11-15 21:14 ` Tim Cross
2017-11-16 10:05 ` Alain.Cochard
2017-11-15 10:49 ` Alain.Cochard
2017-11-15 11:55 ` Nicolas Goaziou
2017-11-15 12:35 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=22989.25593.198323.807112@frac.u-strasbg.fr \
--to=alain.cochard@unistra.fr \
--cc=emacs-orgmode@gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.