From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Ikumi Keita <ikumi@ikumi.que.jp>
Cc: 58075@debbugs.gnu.org, Juri Linkov <juri@linkov.net>
Subject: bug#58075: Mapping file types to major modes
Date: Thu, 29 Sep 2022 08:18:43 -0400 [thread overview]
Message-ID: <jwvy1u29y04.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <75290.1664427538@localhost> (Ikumi Keita's message of "Thu, 29 Sep 2022 13:58:58 +0900")
> Suppose that a user who prefers built-in TeX modes customized
> `major-mode-remap-alist' via Custom to invalidate site-wide default
> TeX modes and the site admin adds an entry (perl-mode . cperl-mode)
> later. Then the user doesn't see the new site-wide default perl mode.
Indeed, it's a long-standing problem that Customize doesn't let the user
say "I want to add/remove <ELEM>" rather than "I want to set this list to
<VAL>". Actually, strictly speaking it does, but noone bothered to make
that work well.
Stefan
prev parent reply other threads:[~2022-09-29 12:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-25 15:38 bug#58075: Mapping file types to major modes Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-26 11:26 ` Lars Ingebrigtsen
2022-09-26 12:13 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-27 12:54 ` Lars Ingebrigtsen
2022-10-03 15:18 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-03 15:18 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-28 8:15 ` Ikumi Keita
2022-09-28 17:29 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-29 4:58 ` Ikumi Keita
2022-09-29 12:18 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [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
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=jwvy1u29y04.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=58075@debbugs.gnu.org \
--cc=ikumi@ikumi.que.jp \
--cc=juri@linkov.net \
--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).