From: Drew Adams <drew.adams@oracle.com>
To: Emanuel Berg <incal@dataswamp.org>,
"help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: RE: [External] : Re: Matching parenthesis for long constructs
Date: Sat, 11 May 2024 01:43:12 +0000 [thread overview]
Message-ID: <SJ0PR10MB548843DC75D32C9DAA32155DF3E02@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87zfszm21m.fsf@dataswamp.org>
> >> I do not want myself to move from one to another. But to
> >> display for me the line content of the corresponding match
> >> whilst staying at point.
> >
> > Emacs manual, node Matching (Programs > Parentheses >
> > Matching) tells you all you need to know:
>
> But that only helps if the left (opening) parenthesis is in
> the same window, but the OP asked what do when that isn't
> the case.
No. Neither of these require the left, matching
paren to be visible in the same window:
1. 'blink-matching-paren'
2. 'show-paren-context-when-offscreen'
> I agree with him it is a pretty bad state, I think it should
> be outputted in the echo area the same that happens when you
> write a right (closing) parenthesis and the left one isn't in
> the window.
next prev parent reply other threads:[~2024-05-11 1:43 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 [this message]
2024-05-11 5:40 ` tomas
2024-05-09 16:58 ` Heime
2024-05-09 17:45 ` Drew Adams
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=SJ0PR10MB548843DC75D32C9DAA32155DF3E02@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=incal@dataswamp.org \
/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).