bug#45114: perl-mode warns about mismatched parentheses wrongly

bug#45114: perl-mode warns about mismatched parentheses wrongly

[積丹尼 Dan Jacobson]

$ emacs file.pl # and start typing
if(/^[^}]/) ...

During the process you will get spurious warnings about mismatched
parentheses etc.

emacs-version "27.1"

bug#45114: perl-mode warns about mismatched parentheses wrongly

[Eli Zaretskii]

On December 8, 2020 7:45:03 AM GMT+02:00, "積丹尼 Dan Jacobson" <jidanni@jidanni.org> wrote:
> $ emacs file.pl # and start typing
> if(/^[^}]/) ...
> 
> During the process you will get spurious warnings about mismatched
> parentheses etc.
> 
> emacs-version "27.1"

This is a well documented feature.  If you don't like it, turn off blink-matching-paren.

bug#45114: perl-mode warns about mismatched parentheses wrongly

[積丹尼 Dan Jacobson]

>>>>> "EZ" == Eli Zaretskii <eliz@gnu.org> writes:

EZ> This is a well documented feature.  If you don't like it, turn off blink-matching-paren.

But that would ruin it outside of regular expressions too.

bug#45114: perl-mode warns about mismatched parentheses wrongly

[Eli Zaretskii]

On December 8, 2020 8:38:25 AM GMT+02:00, "積丹尼 Dan Jacobson" <jidanni@jidanni.org> wrote:
> >>>>> "EZ" == Eli Zaretskii <eliz@gnu.org> writes:
> 
> EZ> This is a well documented feature.  If you don't like it, turn off
> blink-matching-paren.
> 
> But that would ruin it outside of regular expressions too.

I see nothing special about regular expressions in this context.  Parens matching is useful there as well as anywhere else.

bug#45114: perl-mode warns about mismatched parentheses wrongly

[積丹尼 Dan Jacobson]

>>>>> "EZ" == Eli Zaretskii <eliz@gnu.org> writes:
EZ> I see nothing special about regular expressions in this context.  Parens matching is useful there as well as anywhere else.

/[

means we are entering characters that stand on their own, that _should
not be thought to match_ previous characters.

As I am entering the regexp, emacs should not tell me that

/[}

is wrong.

bug#45114: perl-mode warns about mismatched parentheses wrongly

[Eli Zaretskii]

On December 8, 2020 9:09:51 AM GMT+02:00, "積丹尼 Dan Jacobson" <jidanni@jidanni.org> wrote:
> >>>>> "EZ" == Eli Zaretskii <eliz@gnu.org> writes:
> EZ> I see nothing special about regular expressions in this context. 
> Parens matching is useful there as well as anywhere else.
> 
> /[
> 
> means we are entering characters that stand on their own, that _should
> not be thought to match_ previous characters.
> 
> As I am entering the regexp, emacs should not tell me that
> 
> /[}
> 
> is wrong.

I disagree.

bug#45114: perl-mode warns about mismatched parentheses wrongly

[Harald Jörg]

積丹尼 Dan Jacobson <jidanni@jidanni.org> writes:

> $ emacs file.pl # and start typing
> if(/^[^}]/) ...
>
> During the process you will get spurious warnings about mismatched
> parentheses etc.
>
> emacs-version "27.1"

This is a general Emacs-ism: The warning appears in any mode, not just
in Perl mode.  So, in any environment of Perl mode: in code, but also in
strings, comments, and POD - and in character classes of a regex.
Whenever you type [}, the warning will appear (also in Gnus' message
mode, as I just experienced).

The current message texts "Mismatched parentheses" and "No matching
parenthesis found" _look_ pretty much like error messages from a
compiler, or from a syntax-aware programming mode. They always make me
wince.

I suggest to change the message texts to clarify that no effort was
taken to find out whether the mismatch is significant, like this:

   Note: no matching paren shown

Would that be acceptable?

I guess this bug can be merged with Bug#24299?
-- 
Cheers,
haj

bug#45114: perl-mode warns about mismatched parentheses wrongly

[Stefan Kangas]

forcemerge 24299 45114
thanks

haj@posteo.de (Harald Jörg) writes:

> I guess this bug can be merged with Bug#24299?

Yes, done.