GNU bug report logs - #45114
perl-mode warns about mismatched parentheses wrongly

Previous Next

Package: emacs;

Reported by: 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>

Date: Tue, 8 Dec 2020 05:46:01 UTC

Severity: minor

Tags: confirmed

Merged with 24299

Found in version 26.2

Full log


Message #26 received at 45114 <at> debbugs.gnu.org (full text, mbox):

From: haj <at> posteo.de (Harald Jörg)
To: 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>
Cc: Eli Zaretskii <eliz <at> gnu.org>, 45114 <at> debbugs.gnu.org
Subject: Re: bug#45114: perl-mode warns about mismatched parentheses wrongly
Date: Tue, 08 Dec 2020 12:13:47 +0100
積丹尼 Dan Jacobson <jidanni <at> 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




This bug report was last modified 4 years and 249 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.