From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: van@scratch.space, emacs-devel@gnu.org
Subject: RE: New behavior
Date: Sun, 16 Sep 2018 11:09:33 -0700 (PDT) [thread overview]
Message-ID: <ba425763-6bd0-445a-a77b-34bac0bb2638@default> (raw)
In-Reply-To: <<83zhwhgyv5.fsf@gnu.org>>
> > That users should not, and generally do not, need to know Lisp
> > to customize a user option is not a reason that the doc for that
> > option should not mention the Lisp values. It's true that there
> > is no obligation for the doc to mention the Lisp values, but it
> > generally helps users to do so - so it typically _should_.
>
> There's also no catastrophe if users will read the source to find that
> out. Especially those who want to know and use Lisp.
No catastrophe, no. No catastrophe even if Emacs provided no
doc strings anywhere.
The point is that doc helps users, including those who, like you
and me, generally have no problem reading the source code.
Being able to consult the source code is the best thing about
Emacs. But being able to do that is not a reason not to help
users by describing argument values and option values in
doc strings.
prev parent reply other threads:[~2018-09-16 18:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-13 17:40 New behavior Bruce Korb
2018-09-13 17:50 ` Stephen Berman
2018-09-13 18:01 ` Eli Zaretskii
2018-09-13 18:04 ` Bruce Korb
2018-09-13 18:18 ` Eli Zaretskii
2018-09-14 9:49 ` Van L
2018-09-14 10:37 ` Phil Sainty
2018-09-14 12:36 ` Eli Zaretskii
2018-09-16 13:39 ` Van L
2018-09-16 16:14 ` Eli Zaretskii
2018-09-17 1:34 ` Van L
2018-09-17 2:39 ` Eli Zaretskii
2018-09-18 0:02 ` Van L
2018-09-18 8:19 ` Eli Zaretskii
2018-09-19 18:03 ` Bingo
2018-09-19 18:16 ` Davis Herring
2018-09-19 18:46 ` Bingo
2018-09-20 6:02 ` Van L
[not found] ` <<837ejlifmy.fsf@gnu.org>
2018-09-16 16:29 ` Drew Adams
2018-09-16 17:01 ` Eli Zaretskii
[not found] ` <<<837ejlifmy.fsf@gnu.org>
[not found] ` <<f1ac2978-370e-497c-a809-34d3c8682279@default>
[not found] ` <<83zhwhgyv5.fsf@gnu.org>
2018-09-16 18:09 ` Drew Adams [this message]
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=ba425763-6bd0-445a-a77b-34bac0bb2638@default \
--to=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=van@scratch.space \
/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.