unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: 40119@debbugs.gnu.org
Subject: bug#40119: [PATCH] Make compilation-mode regexp matching case-sensitive
Date: Wed, 18 Mar 2020 21:29:25 +0200	[thread overview]
Message-ID: <837dzhfomi.fsf@gnu.org> (raw)
In-Reply-To: <94F606C0-31BE-4BF3-84B3-64F8BAAF7A58@acm.org> (message from Mattias Engdegård on Wed, 18 Mar 2020 19:30:23 +0100)

> From: Mattias Engdegård <mattiase@acm.org>
> Date: Wed, 18 Mar 2020 19:30:23 +0100
> Cc: 40119@debbugs.gnu.org
> 
> 18 mars 2020 kl. 19.05 skrev Eli Zaretskii <eliz@gnu.org>:
> 
> > What if we are wrong and some compiler needs case-insensitive
> > matching?  Your change makes it impossible to get back the old
> > behavior, not even optionally.
> 
> Do you mean that we should add a defcustom to permit the user to control the behaviour, or that doing so is impossible once rules are added which rely on the case-sensitivity?

The former.

> Either way, it seems much more likely that it is case-insensitivity that is an obstacle to adding new rules, not the contrary.

I don't understand what adding new rules has to do with this.  I'm
talking about a specific rule that needs to be matched
case-insensitively.

> Could you give an example of what such a hypothetical compiler needing case-insensitive matching would look like?

Sorry, I don't understand the question.  What I meant is that some of
the rules were written _knowing_ that the match is case-insensitive,
and will fail to match if that is changed.  I don't think there's
anyone around here that can claim detailed knowledge of every rule and
the compiler(s) that use them, so we have no one to ask whether this
danger is real or imaginary.





  reply	other threads:[~2020-03-18 19:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-18 15:31 bug#40119: [PATCH] Make compilation-mode regexp matching case-sensitive Mattias Engdegård
2020-03-18 18:05 ` Eli Zaretskii
2020-03-18 18:30   ` Mattias Engdegård
2020-03-18 19:29     ` Eli Zaretskii [this message]
2020-03-18 22:05       ` Mattias Engdegård
2020-03-25 20:41         ` Mattias Engdegård
2020-03-25 20:55       ` Dmitry Gutov

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=837dzhfomi.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=40119@debbugs.gnu.org \
    --cc=mattiase@acm.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).