From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Joost Kremers <joostkremers@fastmail.fm>,
57503@debbugs.gnu.org, Robert Pluim <rpluim@gmail.com>,
Philip Kaludercic <philipk@posteo.net>
Subject: bug#57503: 28.1.91; package-selected-packages should not be saved to custom-file
Date: Sun, 04 Sep 2022 12:52:47 +0200 [thread overview]
Message-ID: <871qsrbedc.fsf@gnus.org> (raw)
In-Reply-To: <CADwFkm=ybX69kpOan3h+jkuHSoCFagBGY=Z0z_hR=vba+S++sA@mail.gmail.com> (Stefan Kangas's message of "Sat, 3 Sep 2022 08:32:26 -0700")
Stefan Kangas <stefankangas@gmail.com> writes:
> - Keep the old defcustom, and add a new multisession variable.
>
> - If the old variable exists, use it. Otherwise the new one.
>
> - Add a new command that "upgrades" the variable into a multisession
> variable. Make it say that it will break things on Emacs < 29. Don't
> run it automatically.
>
> - In Emacs version N (e.g., 5 major versions from now?), upgrade any
> user automatically, without prompting, and make the defcustom
> obsolete.
Hm... I think this has the disadvantage that it both requires user
intervention, but in addition it'll force you into one usage pattern or
another at some point.
I think perhaps Stefan M's suggestion of adding a new user option to
control the behaviour here is the only practical way forward.
next prev parent reply other threads:[~2022-09-04 10:52 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 12:43 bug#57503: 28.1.91; package-selected-packages should not be saved to custom-file Joost Kremers
2022-09-02 13:11 ` Philip Kaludercic
2022-09-02 13:17 ` Robert Pluim
2022-09-02 13:17 ` Lars Ingebrigtsen
2022-09-02 14:33 ` Robert Pluim
2022-09-03 9:52 ` Lars Ingebrigtsen
2022-09-03 10:17 ` Philip Kaludercic
2022-09-03 12:25 ` Lars Ingebrigtsen
2022-09-03 15:32 ` Stefan Kangas
2022-09-04 10:52 ` Lars Ingebrigtsen [this message]
2022-09-05 7:37 ` Robert Pluim
2022-09-05 11:16 ` Lars Ingebrigtsen
2022-09-05 11:51 ` Robert Pluim
2022-09-05 13:14 ` Robert Pluim
2022-09-05 19:04 ` Lars Ingebrigtsen
2022-09-06 8:18 ` Robert Pluim
2022-09-06 10:34 ` Lars Ingebrigtsen
2022-09-06 13:49 ` Robert Pluim
2022-09-06 14:30 ` Robert Pluim
2022-09-06 16:45 ` jakanakaevangeli
2022-09-07 0:09 ` Stefan Kangas
2022-09-07 5:38 ` jakanakaevangeli
2022-09-07 9:55 ` Robert Pluim
2022-09-07 12:39 ` Lars Ingebrigtsen
2022-09-03 15:33 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=871qsrbedc.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=57503@debbugs.gnu.org \
--cc=joostkremers@fastmail.fm \
--cc=philipk@posteo.net \
--cc=rpluim@gmail.com \
--cc=stefankangas@gmail.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 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).