From: "Drew Adams" <drew.adams@oracle.com>
To: "'Stefan Monnier'" <monnier@iro.umontreal.ca>,
"'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 14:03:47 -0800 [thread overview]
Message-ID: <EADAFCC5A7E74062AC66C0B86FC2132A@us.oracle.com> (raw)
In-Reply-To: <jwv4nh89dcs.fsf-monnier+emacs@gnu.org>
> > 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.
>
> Agreed,
Are you not just focusing on the local-variable use case?
What about the case of a global user preference wrt the regexp to use?
Isn't it likely that some users customize this (i.e., as an option), to get a
different general behavior globally? This option has been around for a very
long time.
Why not provide for both: (a) a general (global) user preference for the default
regexp to use and (b) local behavior that deviates from that behavior?
IOW, add a non-option variable, instead of just replacing the existing option
with a non-option variable.
next prev parent reply other threads:[~2013-02-19 22:03 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
2013-02-19 21:57 ` Stefan Monnier
2013-02-19 22:03 ` Drew Adams [this message]
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=EADAFCC5A7E74062AC66C0B86FC2132A@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=13731@debbugs.gnu.org \
--cc=bzg@altern.org \
--cc=monnier@iro.umontreal.ca \
--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.