From: goncholden via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 54551@debbugs.gnu.org
Subject: bug#54551: show-paren-mode inconsistency
Date: Fri, 25 Mar 2022 07:10:36 +0000 [thread overview]
Message-ID: <S5fdNh4ojvyLYvQn5Nw_DW2SzwIqR1BEzWn_zX5G9ZZFyppy_9zWi7H4bvuuSX9MMaYEwnGu7kl2f_2C_Q3uDopcJ_vx-WUN6Ero0rUkIgg=@protonmail.com> (raw)
In-Reply-To: <837d8icyva.fsf@gnu.org>
------- Original Message -------
On Friday, March 25th, 2022 at 6:47 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> > Date: Thu, 24 Mar 2022 22:48:35 +0000
> > From: goncholden goncholden@protonmail.com
> > Cc: 54551@debbugs.gnu.org
> >
> > Consider the following command
> >
> > (setq initial-frame-alist '((width . 72) (height . 26)) ).
> >
> > Would be instructive that when one puts the cursor in the space between (width . 72) and (height . 26), the entire (width . 72) (height . 26) would be highlighted.
>
> Why only "(width . 72) (height . 26)" and not the entire setq expression?
>
> Or maybe I don't understand what you mean by "instructive", i.e. what
>
> exactly would you like Emacs to show you and why?
>
> show-paren-mode has a specific goal: to show you the matching
>
> parenthesis in an unobtrusive way, and do that as you type as well as
>
> when you move through the code. That is the "instructive" role that
>
> it takes up upon itself. It sounds like you want something else,
>
> which would then call for a different feature with different visuals
>
> (parenthesized expressions tend to nest, so being "inside" one of them
>
> means you are "inside" all of the outer ones, and displaying them
>
> calls for a different technique than what show-paren does).
>
> > But (setq show-paren-when-point-inside-paren t) does not do that.
> >
> > Can be very non-intuitive when debugging.
>
> For debugging, I suggest that you use C-M-u.
>
> > Also, if you put the cursor on the parenthesis following (height . 26), only (height . 26) gets highlighted, rather than the entire (height . 26) (height . 26).
>
> What do you mean by "the entire (height . 26)"? Did you try to set
> show-paren-style to 'expression', and if not, does it do what you
> want?
I had been trying "(customize-set-variable 'show-paren-when-point-inside-paren t)".
It has been suggested to me to try "highlight-sexp", which seems to work better than
the functionality provided by show-paren-when-point-inside-paren.
With "highlight-sexp", placing cursor after "(width . 72)" does highlight
"(width . 72) (height . 26)" for the expression
"(setq initial-frame-alist '((width . 72) (height . 26)) )"
"highlight-sexp" does highlight the innermost expression, not so with
"show-paren-when-point-inside-paren".
You are making sense, but I wondered if you could see possibilities for
improvements to "show-paren-mode".
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.
next prev parent reply other threads:[~2022-03-25 7:10 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 [this message]
2022-03-25 7:21 ` Eli Zaretskii
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='S5fdNh4ojvyLYvQn5Nw_DW2SzwIqR1BEzWn_zX5G9ZZFyppy_9zWi7H4bvuuSX9MMaYEwnGu7kl2f_2C_Q3uDopcJ_vx-WUN6Ero0rUkIgg=@protonmail.com' \
--to=bug-gnu-emacs@gnu.org \
--cc=54551@debbugs.gnu.org \
--cc=eliz@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).