From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 27348@debbugs.gnu.org
Subject: bug#27348: 24.5; [PATCH] let defvars benefit from defcustom keywords and persistence
Date: Mon, 24 Jun 2019 11:04:40 -0700 (PDT) [thread overview]
Message-ID: <30a84ebd-5903-4e74-8083-48b2f6cddabd@default> (raw)
In-Reply-To: <m3a7e7rlfq.fsf@gnus.org>
> > The ability to type-check, provide :set and :initialize trigger
> > functions, automatically :require libraries, add links to doc, associate
> > with one or more :groups, etc. - these are useful things to be able to
> > do with at least some defvars, not just with defcustoms. Similarly, the
> > ability to persist non-option variables in a user's custom file can be
> > useful.
>
> I think this is an interesting idea, but perhaps a bug report isn't the
> right venue for it? Did you take this up on emacs-devel?
>
> (And here's my two pennies on the subject after considering it for about
> 60 seconds: I'm not sure this sort of extension of the type system is
> that useful... If we want a more expressive type system in Emacs, this
> is the wrong place to start.)
It's an enhancement request. This is the place for that.
And yes, I brought it up on emacs-devel some time ago.
(Probably was told to file an enhancement request. ;-))
This is not an "extension of the [Lisp] type system".
It simply gives Lisp programmers the ability to use
some `defcustom' features for variables that users
do not change using Customize.
It separates such features, which are useful for
programmers, from the use of Customize.
next prev parent reply other threads:[~2019-06-24 18:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-12 21:34 bug#27348: 24.5; [PATCH] let defvars benefit from defcustom keywords and persistence Drew Adams
2019-06-24 16:35 ` Lars Ingebrigtsen
2019-06-24 18:04 ` Drew Adams [this message]
2020-08-10 15:04 ` Lars Ingebrigtsen
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=30a84ebd-5903-4e74-8083-48b2f6cddabd@default \
--to=drew.adams@oracle.com \
--cc=27348@debbugs.gnu.org \
--cc=larsi@gnus.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).