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: Sun, 30 Jul 2023 12:27:38 +0200 [thread overview]
Message-ID: <87tttk7e01.fsf@gmail.com> (raw)
In-Reply-To: <83jzuhlnrk.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 10:28:14 +0200
>>
>>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>> > That line _is_ matched by auto-mode-interpreter-regexp:
>> >
>> > (string-match-p auto-mode-interpreter-regexp
>> > "#!/usr/bin/env
>> > -S ruby -e 'puts 123'") => 0
>> >
>> > The problem is how to find the name of the interpreter if the
>> > text
>> > after "/usr/bin/env" includes more than one word? Once we
>> > start
>> > using command-line switches and their arguments, and take
>> > into
>> > consideration that many GNU/Linux programs can freely
>> > intersperse
>> > options and non-option arguments on the command line in any
>> > order,
>> > where does this end?
>>
>> I am hoping there is some way of effectively matching
>> command-line
>> switches for '/usr/bin/env', but sounds like it is perhaps too
>> complex?
>
> How can we do that without incurring non-trivial maintenance
> costs?
> 'env' is being actively developed; e.g., the old version I have
> where
> I'm typing this doesn't even have the -S option. Are we
> supposed to
> track every new command-line option added to 'env', and update
> our
> code accordingly? That is even impractical, because someone
> could use
> 2-year old Emacs with Coreutils released just yesterday.
No, I don't think we should track every command-line option added,
but
just allow to match command-line options for env ( maybe this is
the
non-trivial part). I don't understand why it will have an impact
for
someone who is using a version 5+ year old version of Coreutils.
If it was possible for a user to add configuration to
set-auto-mode
script files like the ones mentioned above I think this will be
less of
an issue.
next prev parent reply other threads:[~2023-07-30 10:27 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
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 [this message]
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=87tttk7e01.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).