From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Po Lu <luangruo@yahoo.com>
Cc: Eli Zaretskii <eliz@gnu.org>, acm@muc.de, emacs-devel@gnu.org
Subject: Re: Subversion of user chosen major mode by Emacs. [Was: My usage of imenu is broken.]
Date: Thu, 30 May 2024 11:08:45 -0400 [thread overview]
Message-ID: <jwvo78nwdbw.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87a5k79xnu.fsf@yahoo.com> (Po Lu's message of "Thu, 30 May 2024 22:33:57 +0800")
>> AFAICT it is a lot more common for file-local vars to be abused to
>> specify mere user preferences, than the reverse (i.e. where there really
>> is a technical reason why the file should be edited with js2-mode rather
>> than js-mode).
> True, but this doesn't answer Eli's question.
No, I didn't feel the need to repeat your answer.
And of course there are various other solutions: this is Emacs we're
talking about, so you can "always" code-your way around any special case.
E.g. it's easy enough to
(defalias 'cc-c-mode #'c-mode)
and then use
-*- cc-c -*-
And if it ever turns into a common enough need, it'll be easy to
streamline one of those solutions.
Stefan
next prev parent reply other threads:[~2024-05-30 15:08 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 10:53 My usage of imenu is broken Alan Mackenzie
2024-05-28 11:34 ` Eli Zaretskii
2024-05-28 13:57 ` Alan Mackenzie
2024-05-28 18:29 ` Eli Zaretskii
2024-05-28 20:46 ` Alan Mackenzie
2024-05-28 21:28 ` Stefan Monnier
2024-05-29 6:04 ` Juri Linkov
2024-05-29 11:31 ` Eli Zaretskii
2024-05-29 5:38 ` Yuan Fu
2024-05-28 21:55 ` Stefan Monnier
2024-05-29 11:16 ` Subversion of user chosen major mode by Emacs. [Was: My usage of imenu is broken.] Alan Mackenzie
2024-05-29 11:43 ` Dmitry Gutov
2024-05-29 12:51 ` Subversion of user chosen major mode by Emacs Alan Mackenzie
2024-05-29 16:08 ` Dmitry Gutov
2024-05-29 16:38 ` Eli Zaretskii
2024-05-29 17:56 ` Dmitry Gutov
2024-05-29 19:22 ` Alan Mackenzie
2024-05-29 19:45 ` Andrea Corallo
2024-05-29 19:59 ` Alan Mackenzie
2024-05-30 5:01 ` Eli Zaretskii
2024-05-30 11:02 ` Alan Mackenzie
2024-05-29 22:10 ` Dmitry Gutov
2024-05-30 5:51 ` Eli Zaretskii
2024-05-30 5:44 ` Eli Zaretskii
2024-05-29 12:41 ` Subversion of user chosen major mode by Emacs. [Was: My usage of imenu is broken.] Eli Zaretskii
2024-05-29 13:29 ` Subversion of user chosen major mode by Emacs Alan Mackenzie
2024-05-29 14:20 ` Eli Zaretskii
2024-05-29 15:04 ` Stefan Monnier
2024-05-29 19:17 ` Subversion of user chosen major mode by Emacs. [Was: My usage of imenu is broken.] Eli Zaretskii
2024-05-30 1:32 ` Stefan Monnier
2024-05-30 5:25 ` Eli Zaretskii
2024-05-30 7:39 ` Po Lu
2024-05-30 7:53 ` Eli Zaretskii
2024-05-30 14:18 ` Stefan Monnier
2024-05-30 14:33 ` Po Lu
2024-05-30 15:08 ` Stefan Monnier [this message]
2024-05-30 14:56 ` Eli Zaretskii
2024-05-30 15:12 ` Stefan Monnier
2024-05-30 15:29 ` Alan Mackenzie
2024-05-30 18:30 ` Stefan Monnier
2024-05-30 16:06 ` Eli Zaretskii
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=jwvo78nwdbw.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=acm@muc.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.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).