unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Bastien'" <bzg@altern.org>, "'T.V. Raman'" <tv.raman.tv@gmail.com>
Cc: 13731@debbugs.gnu.org
Subject: bug#13731: 24.3.50; C-h N -- Outline navigation Fails
Date: Tue, 19 Feb 2013 11:23:20 -0800	[thread overview]
Message-ID: <6C20A984A05D40E0A69AB390817CD69A@us.oracle.com> (raw)
In-Reply-To: <87y5ek1diw.fsf@bzg.ath.cx>

> > 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_.  The recommended way to set (i.e., customize) it should
be to use Customize.  Users do not necessarily even have a particular file
within which using Local Variables would make sense for 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.

If you want to say that you recommend that Lisp code that sets the value use
Local Variables, that would presumably be OK as far as it goes.  But the general
idea is that Lisp code should not trample on user option values.

And note that nothing else in file outline.el mentions the fact that
`outline-regexp' is likely to be buffer-local.

It seems that that statement has been in the doc string from the beginning - at
least as far back as Emacs 20.  I still think it is misguided.

The same recommendation appears in (emacs) `Outline Format':

  You can customize the criterion for distinguishing heading lines by
  setting the variable `outline-regexp'.  (The recommended ways to do
  this are in a major mode function or with a file local variable.)  Any
  line whose beginning has a match for this regexp is considered a
  heading line.  Matches that start within a line (not at the left
  margin) do not count.

That hardly sounds like the kind of user customization of a defcustom that Emacs
recommends in general.  Sounds like something to be recommended for a defvar
value instead.

Just one opinion.






  reply	other threads:[~2013-02-19 19:23 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 [this message]
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
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=6C20A984A05D40E0A69AB390817CD69A@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 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).