all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lekktu@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 14591@debbugs.gnu.org
Subject: bug#14591: New keyword :local for defcustom
Date: Thu, 13 Jun 2013 16:25:04 +0200	[thread overview]
Message-ID: <CAAeL0SRXrojFdvzxBQ1Z5njk6_XmoAPUifrz4L71sm42gm5Esw@mail.gmail.com> (raw)
In-Reply-To: <jwvtxl2f66j.fsf-monnier+emacs@gnu.org>

> But: is it important for those to be "not automatically buffer-local",
> or would it be OK for them to be automatically buffer-local.

Well, that's a good question.

The first example I can think of is one variable I'm really puzzled is
not automatically buffer-local, because it is *always* used as so (I
checked), revert-buffer-function. The only case in the sources where
it is not assigned with (set (make-local-variable
'revert-buffer-function) ...) is in dired-x.el, and that because at
that point is already guaranteed that dired-mode.el made it a-b-l.

So, it's important for revert-buffer-function to be "not automatically
buffer-local"? Does it even make sense that it is not? :-)

   J





  reply	other threads:[~2013-06-13 14:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-11 17:18 bug#14591: New keyword :local for defcustom Juanma Barranquero
2013-06-11 21:01 ` Ted Zlatanov
2013-06-12 17:27 ` Glenn Morris
2013-06-13  1:57   ` Juanma Barranquero
2013-06-13 14:16     ` Stefan Monnier
2013-06-13 14:25       ` Juanma Barranquero [this message]
2013-06-13 19:53         ` Stefan Monnier
2013-06-14 13:06           ` Juanma Barranquero
2019-06-27 11:28             ` Lars Ingebrigtsen
2019-06-28 11:04               ` Juanma Barranquero
2013-06-14 13:03   ` Juanma Barranquero
2013-06-12 18:56 ` Stefan Monnier
2013-06-13  2:01   ` Juanma Barranquero

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=CAAeL0SRXrojFdvzxBQ1Z5njk6_XmoAPUifrz4L71sm42gm5Esw@mail.gmail.com \
    --to=lekktu@gmail.com \
    --cc=14591@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.