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 10:28:14 +0200 [thread overview]
Message-ID: <87351591ue.fsf@gmail.com> (raw)
In-Reply-To: <83zg3eknjd.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Wilhelm Kirschbaum <wkirschbaum@gmail.com>
>> Date: Sat, 29 Jul 2023 22:08:19 +0200
>>
>>
>> A file without an extension will load ruby-mode if the first
>> line
>> is:
>>
>> #!/usr/bin/env ruby
>>
>> but not when the first line is:
>>
>> #!/usr/bin/env -S ruby -e 'puts 123'
>>
>> Is there any reason why the latter should not be matched by the
>> default
>> `auto-mode-interpreter-regexp' value in 'files.el'?
>
> 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?
This probably ends with a match to some common command-line
variations
for the '/usr/bin/env' program. It is not complete now, so make
it
guess slightly better is perhaps appropriate?
>> A more useful example I stumbled on today while working on a
>> language
>> server after adding:
>>
>> `(add-to-list 'interpreter-mode-alist '("elixir"
>> . elixir-ts-mode))'
>>
>>
>> #!/usr/bin/env -S elixir --erl "-kernel
>> standard_io_encoding
>> latin1"
>
> How about making a script that invokes elixir with those
> arguments,
> and then augment interpreter-mode-alist to name that script
> instead?
That is an option, but then I have to convince the maintainers of
all the packages I work on to make this change, vs my editor
handling this.
Even locally changing the regexp means that the match index has
changed, so
can't see this working without a patch.
If this is perhaps too much work and/or uncertainty for negligible
benefit to users, then it won't cause distress on my side :).
Wilhelm
next prev parent reply other threads:[~2023-07-30 8:28 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87351591ue.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.