From: "Drew Adams" <drew.adams@oracle.com>
To: "'Bastien'" <bzg@altern.org>
Cc: "'T.V. Raman'" <tv.raman.tv@gmail.com>, 13731@debbugs.gnu.org
Subject: bug#13731: 24.3.50; C-h N -- Outline navigation Fails
Date: Tue, 19 Feb 2013 12:49:22 -0800 [thread overview]
Message-ID: <AA801141EB654C63BC34FF37EDB480BB@us.oracle.com> (raw)
In-Reply-To: <87d2vwgksf.fsf@bzg.ath.cx>
> > I'd say that that is a doc bug.
> >
> > This is a _user option_.
>
> Well, I would say this calls for making it a variable instead of an
> option. This is what we do for org-outline-regexp for example.
That's what I meant by this:
> I suggest we remove that recommendation from the doc string.
> Or we change the status of this variable from a defcustom to
> a defvar.
^^^^^^
The question comes down to the kinds of "customization" we really expect from
users. If we expect that they will want to change the var value globally, then
a user option is appropriate. If we expect them to change it using Lisp, and
perhaps locally, then a non-option variable is appropriate.
And if we expect both possibilities then we can have both: an option and a
separate variable. We can decide which takes precedence and document that.
Yes, it can be reasonable (IMO, but others might disagree) to allow the
non-option var to take precedence, i.e., to allow the user option to be
overruled by code, provided this is well documented so users know what to
expect.
next prev parent reply other threads:[~2013-02-19 20:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-16 19:08 bug#13731: 24.3.50; C-h N -- Outline navigation Fails raman
2013-02-16 19:31 ` Glenn Morris
2013-02-16 20:04 ` T. V. Raman
2013-02-16 20:18 ` Eli Zaretskii
2013-02-17 2:45 ` T. V. Raman
2013-02-17 2:48 ` T.V. Raman
2013-02-17 3:49 ` Eli Zaretskii
2013-02-19 1:42 ` T.V. Raman
2013-02-19 15:56 ` Bastien
2013-02-19 19:23 ` Drew Adams
2013-02-19 19:34 ` Bastien
2013-02-19 20:49 ` Drew Adams [this message]
2013-02-19 21:57 ` Stefan Monnier
2013-02-19 22:03 ` Drew Adams
2013-02-20 2:20 ` T. V. Raman
2013-02-20 13:08 ` Bastien
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=AA801141EB654C63BC34FF37EDB480BB@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=13731@debbugs.gnu.org \
--cc=bzg@altern.org \
--cc=tv.raman.tv@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 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.