GNU bug report logs - #54551
show-paren-mode inconsistency

Previous Next

Full log

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

From: Stephen Berman <stephen.berman <at> gmx.net>
To: goncholden <goncholden <at> protonmail.com>
Cc: 54551 <at> debbugs.gnu.org
Subject: Re: bug#54551: show-paren-mode inconsistency
Date: Fri, 25 Mar 2022 13:00:34 +0100

On Fri, 25 Mar 2022 11:56:50 +0000 goncholden <goncholden <at> protonmail.com> wrote:

> ------- Original Message -------
>
> On Friday, March 25th, 2022 at 11:47 PM, goncholden
> <goncholden <at> protonmail.com> wrote:
>
>> ------- Original Message -------
>>
>> On Friday, March 25th, 2022 at 8:51 PM, Stephen Berman
>> stephen.berman <at> gmx.net wrote:
>>
>> > On Fri, 25 Mar 2022 07:10:36 +0000 goncholden via "Bug reports for GNU
>> > Emacs, the Swiss army knife of text editors" bug-gnu-emacs <at> gnu.org wrote:
>> >
>> > > I am debugging a problem where emacs states that there exists an extra
>> > >
>> > > closing parenthesis, but having extreme difficulty locating it.
>> > >
>> > > Have split the file in two and using "require" on a child file. Otherwise
>> > >
>> > > I have to comment each line of code rather than whole sections. Commenting
>> > >
>> > > each line is likely to introduce errors if one is not very careful removing
>> > >
>> > > the comment tags.
>> >
>> > Have you tried calling `check-parens' in the files?
>> >
>> > Steve Berman
>>
>> Have not played with that, no.
>
> Need some assistance on using check-parens.  Have done
> "M-x check-parens", what do I have to do after that, and what should I check?

If `check-parens' finds an unbalanced parenthesis, it moves point to
that position.  If point doesn't change in the buffer you called
`check-parens' in, then that buffer has no unbalanced parentheses.

Steve Berman

Previous Next

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