From: "T. V. Raman" <tv.raman.tv@gmail.com>
To: bzg@altern.org
Cc: 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 18:20:54 -0800 [thread overview]
Message-ID: <20772.13062.805772.262442@gargle.gargle.HOWL> (raw)
In-Reply-To: <87d2vwgksf.fsf@bzg.ath.cx>
My recommendation is that this be made a defvar -- letting
custom touch this variable is hard to debug --
>>>>> "Bastien" == Bastien <bzg@altern.org> writes:
Bastien> Hi Drew, "Drew Adams" <drew.adams@oracle.com>
Bastien> writes:
Bastien>
>>> > outline-regexp is customizable, and its default value
>>> had gotten > changed in my customization settings at some
>>> point. Would be > wise for C-h N to set outline-regexp
>>> appropriately -- perhaps > via a file-local variable in
>>> the News file?
>>>
>>> The docstring of `outline-regexp' says The recommended
>>> way to set this is with a Local Variables: list in the
>>> file it applies to. So I'd suggest to simply follow the
>>> recommendation here.
>>
>> I'd say that that is a doc bug.
>>
>> This is a _user option_.
Bastien>
Bastien> Well, I would say this calls for making it a
Bastien> variable instead of an option. This is what we do
Bastien> for org-outline-regexp for example.
Bastien>
Bastien> -- Bastien
--
Best Regards,
--raman
next prev parent reply other threads:[~2013-02-20 2:20 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
2013-02-20 2:20 ` T. V. Raman [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20772.13062.805772.262442@gargle.gargle.HOWL \
--to=tv.raman.tv@gmail.com \
--cc=13731@debbugs.gnu.org \
--cc=bzg@altern.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.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).