From: Emanuel Berg <incal@dataswamp.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Matching parenthesis for long constructs
Date: Thu, 09 May 2024 17:38:37 +0200 [thread overview]
Message-ID: <87wmo3m1vm.fsf@dataswamp.org> (raw)
In-Reply-To: CALTqLiaHVi5Bj7OXAXMeBv+1QRBQLQRyMz3Ef=pnBsc-6Jb02Q@mail.gmail.com
Pierre Rouleau wrote:
> in the current window, split that window vertically (C-x 3)
> as many times are required to see the end of the function
> inside the other window.
One shouldn't have to do anything for this.
> Several packages support parenthesis highlighting. Lispy is
> one of them.
One shouldn't have to install anything for this and it should
be the default behavior.
Also highlighting in its basic form does not help if one of
the parenthesis isn't in the window so cannot be highlighted
for that very reason, this was very clearly explained by the
OP in the initial post.
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2024-05-09 15:38 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
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 [this message]
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=87wmo3m1vm.fsf@dataswamp.org \
--to=incal@dataswamp.org \
--cc=help-gnu-emacs@gnu.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).