unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
	Emacs developers <emacs-devel@gnu.org>
Subject: Re: [Emacs-diffs] master 4449301: * etc/NEWS: Improve documentation of 'package-initialize'.
Date: Mon, 18 Nov 2019 16:05:22 +0100	[thread overview]
Message-ID: <CADwFkmnR2dhQ9EFu6xTpOfK6KF12DHO-q-xjVBKbMtq2yk8oAw@mail.gmail.com> (raw)
In-Reply-To: <83ftiq7lob.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> writes:

> I'm not sure I understand how grave are the problems with this

The only problem is that it doesn't work.  :-)

To be more specific: When a user customizes this variable to nil, it
doesn't take effect.  As Stefan Monnier pointed out in this thread, it
*does* take effect iff the user loads the custom file from the early
init file.  I opined that this is probably not the most common use
pattern.

> defcustom, but if they are, I'd prefer to add a :set function rather
> than demoting a user option to a defvar.

OK, let's try that instead.  Please also see my other recent email in
this thread.

Best regards,
Stefan Kangas



  reply	other threads:[~2019-11-18 15:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20191022021600.2389.91268@vcs0.savannah.gnu.org>
     [not found] ` <20191022021602.B41B3209DE@vcs0.savannah.gnu.org>
2019-10-22 12:28   ` [Emacs-diffs] master 4449301: * etc/NEWS: Improve documentation of 'package-initialize' Stefan Monnier
2019-10-23 12:12     ` Stefan Kangas
2019-10-23 12:49       ` Stefan Monnier
2019-11-02  4:57         ` Stefan Kangas
2019-11-04 17:53           ` Stefan Monnier
2019-11-11 16:07             ` Stefan Kangas
2019-11-12 15:50               ` Stefan Monnier
2019-11-18 14:58                 ` Stefan Kangas
2019-11-14 11:16               ` Eli Zaretskii
2019-11-18 15:05                 ` Stefan Kangas [this message]
2019-11-02  3:34       ` Stefan Kangas

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=CADwFkmnR2dhQ9EFu6xTpOfK6KF12DHO-q-xjVBKbMtq2yk8oAw@mail.gmail.com \
    --to=stefankangas@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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 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).