From: Malcolm Cook <malcolm.cook@gmail.com>
To: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
Cc: Wilhelm Kirschbaum <wkirschbaum@gmail.com>,
64939@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#64939: 30.0.50; The default auto-mode-interpreter-regexp does not match env with flags
Date: Sat, 10 Feb 2024 11:23:11 -0600 [thread overview]
Message-ID: <CAAAQmVZDuvQ=tZ=1+7ZbAsCGsrsQsr1gdSrDmfukqZ4Og48KdQ@mail.gmail.com> (raw)
In-Reply-To: <87v86wtfgd.fsf@gmail.com>
Hooray - thanks - all seems perfect to me
On Sat, Feb 10, 2024 at 11:08 AM Kévin Le Gouguec
<kevin.legouguec@gmail.com> wrote:
>
> Kévin Le Gouguec <kevin.legouguec@gmail.com> writes:
>
> > Is this Good Enough™ for your purposes (Malcolm, Wilhelm), or should we
> > sophisticate the regexp further? FWIW, in no particular order:
> >
> > (a) env(1) does seem to support mixing up arbitrary options with -S¹, so
> > in principle it would make sense to support that;
> >
> > (b) Eli did not seem too found of the regexp hammer², so I don't know
> > which direction we'd want to go between maximally correct (accept
> > all arguments, _as long as_ -S|--split-string is in there) or good
> > enough (just skip over --everything --that --looks --like -a
> > --switch).
> >
> > (c) FWIW the "maximally correct" regexp might not be _that_ ugly, since
> > "-[v]S[OPTION]" must be the *first* token after env; in other words
> > no need to support --some-option --split-string --more-options.
>
> Well, sorry, couldn't resist. How do the attached patches look? The
> new testcases should tell the whole story.
>
> ('make && make -C test files-tests' seems none the worse for wear)
>
--
~ Malcolm Cook
next prev parent reply other threads:[~2024-02-10 17:23 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
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 [this message]
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='CAAAQmVZDuvQ=tZ=1+7ZbAsCGsrsQsr1gdSrDmfukqZ4Og48KdQ@mail.gmail.com' \
--to=malcolm.cook@gmail.com \
--cc=64939@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=kevin.legouguec@gmail.com \
--cc=wkirschbaum@gmail.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 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.