GNU bug report logs - #24299
perl-mode: mismatched parenthesis message

Previous Next

Package: emacs;

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

Date: Wed, 24 Aug 2016 14:59:01 UTC

Severity: minor

Tags: confirmed

Merged with 45114

Found in version 26.2

To reply to this bug, email your comments to 24299 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-gnu-emacs <at> gnu.org:
bug#24299; Package emacs. (Wed, 24 Aug 2016 14:59:01 GMT) Full text and rfc822 format available.

Acknowledgement sent to 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>:
New bug report received and forwarded. Copy sent to bug-gnu-emacs <at> gnu.org. (Wed, 24 Aug 2016 14:59:01 GMT) Full text and rfc822 format available.

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

From: 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>
To: bug-gnu-emacs <bug-gnu-emacs <at> gnu.org>
Subject: perl-mode: mismatched parenthesis message
Date: Wed, 24 Aug 2016 20:27:57 +0800
All I know is when inserting the final ], a mismatched parenthesis /
no matching parenthesis found message appeared in the minibuffer
(depending on the code above it. Anyways, both wrong.)

$visit{$visit_id}{name} = $1         if #m!href="/users/(\d+)/profile">([^<]+)!;
     /<img alt="Photo of ([^"]+)/;

Furthermore, that message should be recorded in the C-h e list.

emacs-version "24.5.1"




Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#24299; Package emacs. (Sat, 06 Jul 2019 04:01:02 GMT) Full text and rfc822 format available.

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

From: Stefan Kangas <stefan <at> marxist.se>
To: 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>
Cc: 24299 <at> debbugs.gnu.org
Subject: Re: bug#24299: perl-mode: mismatched parenthesis message
Date: Sat, 6 Jul 2019 06:00:22 +0200
積丹尼 Dan Jacobson <jidanni <at> jidanni.org> writes:

> All I know is when inserting the final ], a mismatched parenthesis /
> no matching parenthesis found message appeared in the minibuffer
> (depending on the code above it. Anyways, both wrong.)
>
> $visit{$visit_id}{name} = $1         if #m!href="/users/(\d+)/profile">([^<]+)!;
>      /<img alt="Photo of ([^"]+)/;

I can reproduce this on Emacs 26.2, but I see this also without the
first line.

In other words, under "emacs -Q" and M-x perl-mode, when I type:

/<img alt="Photo of ([^"

And then type the final "]", I get the message "No matching parenthesis
found".

> Furthermore, that message should be recorded in the C-h e list.

I'm not sure -- should it?

> emacs-version "24.5.1"

Thanks,
Stefan Kangas




Added tag(s) confirmed. Request was from Stefan Kangas <stefan <at> marxist.se> to control <at> debbugs.gnu.org. (Fri, 23 Aug 2019 06:40:04 GMT) Full text and rfc822 format available.

bug Marked as found in versions 26.2. Request was from Stefan Kangas <stefan <at> marxist.se> to control <at> debbugs.gnu.org. (Fri, 23 Aug 2019 06:40:04 GMT) Full text and rfc822 format available.

Forcibly Merged 24299 45114. Request was from Stefan Kangas <stefankangas <at> gmail.com> to control <at> debbugs.gnu.org. (Tue, 08 Dec 2020 12:04:02 GMT) Full text and rfc822 format available.

Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#24299; Package emacs. (Wed, 23 Jun 2021 16:00:02 GMT) Full text and rfc822 format available.

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

From: haj <at> posteo.de (Harald Jörg)
To: 24299 <at> debbugs.gnu.org
Subject: Can we just drop the noise from blink-matching-paren?
Date: Wed, 23 Jun 2021 15:59:00 +0000
The misleading messages are caused by blink-matching-open which is
confused by the quotation mark within the regexp.  There are various
ways to trigger the message in perl-mode (and cperl-mode).  For example,
the closing paren in this line triggers the same message:

  my $text = "(')";

Modes like text-mode also get the noise when you enter a plain old
smiley like :-) or old-fashioned numbered lists like a), b), ...

Can we just drop these messages from blink-matching-open altogether?  I
know that this is a global change in behavior, but in my opinion the
value of the message for the user isn't that great.
-- 
Cheers,
haj




This bug report was last modified 3 years and 356 days ago.

Previous Next


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