unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Heime <heimeborgia@protonmail.com>
Cc: Pierre Rouleau <prouleau001@gmail.com>,
	Heime via Users list for the GNU Emacs text editor
	<help-gnu-emacs@gnu.org>
Subject: RE: [External] : Re: Matching parenthesis for long constructs
Date: Thu, 9 May 2024 17:45:21 +0000	[thread overview]
Message-ID: <SJ0PR10MB54886F8EDD9A81A0C32CA9CDF3E62@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <yMSb7L0Wwi8Gk_3TnJz4soAF7mnIbWqdu2jsykZIrAB5hjAJh6qLSmFJ3i9uWJZkgm9J5teMsm8_UK8qLmIwvkqdOLAbJZZMfHWLlWuDwE4=@protonmail.com>

> Basically the feature is useful only for short expressions.  If the
> opening expression is not on the screen, you cannot tell which grouping
> you are closing off.  Because emacs show you the text of the construct
> that is one level higher up.
> 
> Try going to the closing parenthesis of a pcase construct where the
> closing
> parenthesis start to blink.  You are effectively within the construct that
> encloses the pcase (the construct at the next higher level) and you get
> shown
> that rather than the pcase construct in the echo area.
> 
> You cannot tell what you are closing off.

`M-x report-emacs-bug'

That's for both bugs and enhancement requests.


  reply	other threads:[~2024-05-09 17:45 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-09 12:33 Matching parenthesis for long constructs Heime
2024-05-09 14:00 ` Pierre Rouleau
2024-05-09 14:22   ` Heime
2024-05-09 14:48     ` [External] : " Drew Adams
2024-05-09 15:35       ` Emanuel Berg
2024-05-11  1:43         ` Drew Adams
2024-05-11  5:40         ` tomas
2024-05-09 16:58       ` Heime
2024-05-09 17:45         ` Drew Adams [this message]
2024-05-09 17:52         ` Eli Zaretskii
2024-05-09 18:09           ` Emanuel Berg
2024-05-11  6:27             ` Eli Zaretskii
2024-05-09 18:24         ` Yuri Khan
2024-05-09 18:29           ` Emanuel Berg
2024-05-09 18:57           ` Heime
2024-05-09 19:45             ` Heime
2024-05-09 19:46             ` Yuri Khan
2024-05-09 20:44               ` Drew Adams
2024-05-09 15:14     ` Pierre Rouleau
2024-05-09 15:38       ` Emanuel Berg
2024-05-11  4:58         ` Pierre Rouleau
2024-05-09 14:24   ` Emanuel Berg
2024-05-09 14:20 ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-05-09 21:49 ` Daniel Martín
2024-05-10 19:38   ` tpeplt

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=SJ0PR10MB54886F8EDD9A81A0C32CA9CDF3E62@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=heimeborgia@protonmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=prouleau001@gmail.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. 
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).