all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 27348@debbugs.gnu.org
Subject: bug#27348: 24.5; [PATCH] let defvars benefit from defcustom keywords and persistence
Date: Mon, 10 Aug 2020 17:04:00 +0200	[thread overview]
Message-ID: <87k0y6zgnz.fsf@gnus.org> (raw)
In-Reply-To: <85d6df89-9c08-4927-9b10-93a0b43808a7@default> (Drew Adams's message of "Mon, 12 Jun 2017 14:34:35 -0700 (PDT)")

Drew Adams <drew.adams@oracle.com> writes:

> This is an enhancement request, with a patch.
>
>   [NOTE: I suggested this enhancement to emacs-devel in 2009.  There was
>    exactly one reply, with only this text: "YAGNI".
>    http://lists.gnu.org/archive/html/emacs-devel/2009-10/msg00668.html
>    http://lists.gnu.org/archive/html/emacs-devel/2015-10/msg01481.html]
>
> 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.

So this has been brought up several times, and nobody seems to be
enthusiastic about the idea.  (I'm not either -- if we're extending
Emacs Lisp to support static typing, I think this would be starting in
at the wrong end.)

So I'm closing this bug report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      parent reply	other threads:[~2020-08-10 15: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
2020-08-10 15:04 ` Lars Ingebrigtsen [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=87k0y6zgnz.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=27348@debbugs.gnu.org \
    --cc=drew.adams@oracle.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 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.