From: Eli Zaretskii <eliz@gnu.org>
To: Sean Whitton <spwhitton@spwhitton.name>
Cc: 54977@debbugs.gnu.org
Subject: bug#54977: 29.0.50; Customising eshell-modules-list means you won't get new default entries
Date: Sun, 17 Apr 2022 08:28:08 +0300 [thread overview]
Message-ID: <83a6ckz3br.fsf@gnu.org> (raw)
In-Reply-To: <87a6ckkath.fsf@melete.silentflame.com> (message from Sean Whitton on Sat, 16 Apr 2022 13:55:22 -0700)
> From: Sean Whitton <spwhitton@spwhitton.name>
> Date: Sat, 16 Apr 2022 13:55:22 -0700
>
> Suppose that you use the customisation interface to enable the
> eshell-rebind module, and save the result in your init. Now upstream
> Emacs gains a new on-by-default module, e.g. the recently added
> em-extpipe. While everyone who hasn't customised eshell-modules-list
> gets the new module automatically, you'll have to customise the variable
> again, and you can't even just tick a box to add it, as with the other
> truly optional modules, but must manually insert it at the end of the
> list. This is no good.
>
> How about using two separate defcustoms for these two kinds of entry?
One other idea is to have the default modules not mentioned
explicitly, but instead have some kind of placeholder which stands for
all the default modules. Similar to some path variables that treat an
empty or nil list member as standing for the default value.
next prev parent reply other threads:[~2022-04-17 5:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-16 20:55 bug#54977: 29.0.50; Customising eshell-modules-list means you won't get new default entries Sean Whitton
2022-04-17 5:01 ` Jim Porter
2022-04-17 5:03 ` Sean Whitton
2022-04-17 5:50 ` Jim Porter
2022-04-17 5:28 ` Eli Zaretskii [this message]
2022-04-18 5:07 ` Sean Whitton
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=83a6ckz3br.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=54977@debbugs.gnu.org \
--cc=spwhitton@spwhitton.name \
/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).