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 04:01:26 +0200	[thread overview]
Message-ID: <CAAeL0ST6ys=LDfehpOB4S+j+pzUV_LWkfdRqOJdH_EBOF=m0cw@mail.gmail.com> (raw)
In-Reply-To: <jwva9mv40rs.fsf-monnier+emacs@gnu.org>

On Wed, Jun 12, 2013 at 8:56 PM, Stefan Monnier
<monnier@iro.umontreal.ca> wrote:

> Problem is: most/all of those are in themselves problematic, because
> Customize handles buffer-local variables very poorly.

Well, yes, but a defcustom is just a fancy variable declaration plus
an even fancier interface to setting it. Whether it makes sense for
the variable to be automatically buffer-local or not is independent of
it being a defcustom, as witnessed by the fact that there are already
automatically buffer-local defcustom'ized variables in the sources.

In other words: that customize handles poorly these kind of variables
is a bug in Customize (and so, something to fix some day), not an
intrinsic feature of these variables.

    J





      reply	other threads:[~2013-06-13  2:01 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
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 [this message]

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='CAAeL0ST6ys=LDfehpOB4S+j+pzUV_LWkfdRqOJdH_EBOF=m0cw@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.