unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Pierre Rouleau <prouleau001@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Matching parenthesis for long constructs
Date: Sat, 11 May 2024 00:58:00 -0400	[thread overview]
Message-ID: <CALTqLiYzAcxQXi1neQvx_imahQm2dZ7XTpQNGt7Ra=e3STjTmg@mail.gmail.com> (raw)
In-Reply-To: <87wmo3m1vm.fsf@dataswamp.org>

On Fri, May 10, 2024 at 5:45 PM Emanuel Berg <incal@dataswamp.org> wrote:

> 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.
>
> Perhaps a little clarification is required.
The OP was asking about ways to see both ends of a long construct, stating
that
highlighting was not helping much when one end does not show in the same
window.

I suggested a technique the OP could use (and that I have used often):
activating the follow-mode and splitting the window in 2 or more vertical
windows.
With point on the '(' in the left window you might be able to see the end
paren
inside one of the window to the right (with both being highlighted).
It provides more vertical space to see the entire construct.
It might or might not be enough, but it's more than only 1 window.

I was trying to address the OP last question,
   "Are there future possibilities or capabilities to address this ?",
by explaining a technique that can be used now.

The follow-mode has been available for a while (docs states >= 19.31).
It does not require using the option ‘show-paren-context-when-offscreen’,
only available
on  Emacs >= 29.1.


> > 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.
>
>
Correct.  You don't need Lispy. paren highlighting is available out of the
box.
I mentioned it, because of a previous post.


> 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.
>
> Correct. But see my first comment.


-- 
/Pierre


  reply	other threads:[~2024-05-11  4:58 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
2024-05-11  4:58         ` Pierre Rouleau [this message]
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='CALTqLiYzAcxQXi1neQvx_imahQm2dZ7XTpQNGt7Ra=e3STjTmg@mail.gmail.com' \
    --to=prouleau001@gmail.com \
    --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).