From: Wilhelm Kirschbaum <wkirschbaum@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 64939@debbugs.gnu.org
Subject: bug#64939: 30.0.50; The default auto-mode-interpreter-regexp does not match env with flags
Date: Mon, 31 Jul 2023 09:11:49 +0200 [thread overview]
Message-ID: <87pm487dqg.fsf@gmail.com> (raw)
In-Reply-To: <83ila1lnph.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Wilhelm Kirschbaum <wkirschbaum@gmail.com>
>> Cc: 64939@debbugs.gnu.org
>> Date: Sun, 30 Jul 2023 11:38:06 +0200
>>
>> > Btw, can't you satisfy your needs via file-local variables?
>>
>> Not without convincing the project maintainers to add Emacs
>> specific
>> lines to the code, which I don't really think is appropriate in
>> some
>> cases.
>
> Why not? Many projects add such variables, both for Emacs and
> for
> Vim.
Sure, but its certainly not common on projects I work on where the
vast
majority of the contributors don't care about Emacs.
next prev parent reply other threads:[~2023-07-31 7:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-29 20:08 bug#64939: 30.0.50; The default auto-mode-interpreter-regexp does not match env with flags Wilhelm Kirschbaum
2023-07-29 21:38 ` Wilhelm Kirschbaum
2023-07-30 5:04 ` Eli Zaretskii
2023-07-30 9:38 ` Wilhelm Kirschbaum
2023-07-30 10:04 ` Eli Zaretskii
2023-07-31 7:11 ` Wilhelm Kirschbaum [this message]
2023-07-31 17:38 ` Juri Linkov
2023-08-01 6:20 ` Wilhelm Kirschbaum
2023-07-30 4:53 ` Eli Zaretskii
2023-07-30 8:28 ` Wilhelm Kirschbaum
2023-07-30 10:03 ` Eli Zaretskii
2023-07-30 10:27 ` Wilhelm Kirschbaum
2024-01-31 19:52 ` bug#64939: Malcolm Cook
2024-02-01 18:52 ` bug#64939: Malcolm Cook
2024-02-10 8:27 ` bug#64939: Eli Zaretskii
2024-02-10 10:23 ` bug#64939: 30.0.50; The default auto-mode-interpreter-regexp does not match env with flags Kévin Le Gouguec
2024-02-10 17:08 ` Kévin Le Gouguec
2024-02-10 17:23 ` Malcolm Cook
2024-02-17 8:33 ` Eli Zaretskii
2024-02-28 17:57 ` Wilhelm Kirschbaum
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=87pm487dqg.fsf@gmail.com \
--to=wkirschbaum@gmail.com \
--cc=64939@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).