unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: goncholden <goncholden@protonmail.com>
Cc: 54551@debbugs.gnu.org
Subject: bug#54551: show-paren-mode inconsistency
Date: Fri, 25 Mar 2022 10:21:22 +0300	[thread overview]
Message-ID: <831qyqcxal.fsf@gnu.org> (raw)
In-Reply-To: <S5fdNh4ojvyLYvQn5Nw_DW2SzwIqR1BEzWn_zX5G9ZZFyppy_9zWi7H4bvuuSX9MMaYEwnGu7kl2f_2C_Q3uDopcJ_vx-WUN6Ero0rUkIgg=@protonmail.com> (message from goncholden on Fri, 25 Mar 2022 07:10:36 +0000)

> Date: Fri, 25 Mar 2022 07:10:36 +0000
> From: goncholden <goncholden@protonmail.com>
> Cc: 54551@debbugs.gnu.org
> 
> I am debugging a problem where emacs states that there exists an extra
> closing parenthesis, but having extreme difficulty locating it.

For this, I propose one of the following methods, or their
combination:

  . use C-M-f to move forward by sexps in your init file
  . watch for show-paren to show the closing parenthesis in the
    "mismatched" color

> 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.

You could instead mark a region of the file, and then use
comment-region.

I don't think any of this, or the problem you are trying to solve, is
relevant to what show-paren does, though.





  reply	other threads:[~2022-03-25  7:21 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-24 20:13 bug#54551: show-paren-mode inconsistency goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-24 20:28 ` Eli Zaretskii
2022-03-24 22:48   ` goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-25  0:12     ` Phil Sainty
2022-03-25  4:20       ` goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-25  4:29         ` goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-25  4:57         ` Phil Sainty
2022-03-25  5:23           ` goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-25  5:53             ` Phil Sainty
2022-03-25  6:47     ` Eli Zaretskii
2022-03-25  7:10       ` goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-25  7:21         ` Eli Zaretskii [this message]
2022-03-25  8:35           ` goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-25 10:15             ` Eli Zaretskii
2022-03-25  8:51         ` Stephen Berman
2022-03-25  9:32           ` Phil Sainty
2022-03-25 11:47           ` goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-25 11:56             ` goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-25 12:00               ` Stephen Berman
2022-03-24 21:34 ` Phil Sainty
2022-03-25 16:25   ` Lars Ingebrigtsen

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=831qyqcxal.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=54551@debbugs.gnu.org \
    --cc=goncholden@protonmail.com \
    /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).