all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: 14591@debbugs.gnu.org
Subject: bug#14591: New keyword :local for defcustom
Date: Tue, 11 Jun 2013 17:01:04 -0400	[thread overview]
Message-ID: <m2a9mwcqgf.fsf@lifelogs.com> (raw)
In-Reply-To: <CAAeL0SQbP4dDVtMpveijdynjbuZVtyubrYDjNTL1FH1NRc5D_g@mail.gmail.com>

On Tue, 11 Jun 2013 19:18:54 +0200 Juanma Barranquero <lekktu@gmail.com> wrote: 

JB> This patch adds a new keyword :local to defcustom, to simplify cases like

JB> (defcustom some-var some-val
JB>    "A very long description
JB> filling many lines
JB> ...
JB> ...
JB> ..."
JB>   ;; some keywords)
JB> (make-variable-buffer-local 'some-var)

JB> i.e., it tries to solve the same problem (non-locality) for
JB> customization variables that the new macro defvar-local solves for
JB> defvars.

JB> As designed, it accepts values 'local (which means make the symbol
JB> automatically buffer-local), 'permanent (which makes the symbol
JB> permanent-local), and t which does both.

JB> OK to the idea, the interface, comments...?

I like it.  Also we have `defvoo' in Gnus which is along the same lines
but more aimed at the server data structure than defcustoms.

The interface makes perfect sense to me.

Ted






  reply	other threads:[~2013-06-11 21: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 [this message]
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

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=m2a9mwcqgf.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=14591@debbugs.gnu.org \
    --cc=bug-gnu-emacs@gnu.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 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.