From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Highlighting parentheses when matching parentheses resides outside visible window
Date: Wed, 26 Oct 2022 14:09:47 +0300 [thread overview]
Message-ID: <83eduuon7o.fsf@gnu.org> (raw)
In-Reply-To: <gqMbb77QC8skHnkMNgx9dxmkXHpVUOBn96bsAlGD3yjIp8fsoOHGrcWI3AYDLlHFils41V5y-TAxNzYJ-4m5j6e7HW1UBIt0OhSm60Ha2eI=@protonmail.com> (message from Heime on Tue, 25 Oct 2022 22:41:33 +0000)
> Date: Tue, 25 Oct 2022 22:41:33 +0000
> From: Heime <heimeborgia@protonmail.com>
> Cc: help-gnu-emacs@gnu.org
>
> Have spent some serious time scrutinising show-paren-style.
>
> I will explain the problem. Suppose your function is longer than your emacs window.
> Use "expression" as "show-paren-style", then go just after the last closing parenthesis.
> You get the associated region highlighted. BUT, try to scroll up the code, the highlighting
> get recomputed as the point moves across the window. Thus highlighting capability becomes
> useless when the part does not fit in the emacs window pane.
I'm sorry, but this doesn't explain your problem in enough detail.
First, what exactly do you mean by "scroll up the code"? which Emacs
commands did you use to scroll? At least some ways of scrolling don't
move point.
And when you say "point moves across the window", do you mean that
point moves with the text or that the text moves, but point stays at
the same screen coordinates? Depending on how you scroll, it could be
one or the other.
Next, what do you mean by "highlighting get recomputed as the point
moves across the window"? What happens with highlighting as you
"scroll" that you don't like?
And finally, what would you like to happen instead in this case?
next prev parent reply other threads:[~2022-10-26 11:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 11:22 Highlighting parentheses when matching parentheses resides outside visible window Heime
2022-10-25 11:40 ` Eli Zaretskii
2022-10-25 12:01 ` Heime
2022-10-25 12:44 ` Eli Zaretskii
2022-10-25 22:41 ` Heime
2022-10-26 11:09 ` Eli Zaretskii [this message]
2022-10-26 17:05 ` Heime
2022-10-26 17:37 ` Eli Zaretskii
2022-10-26 17:48 ` Heime
2022-10-26 17:58 ` Eli Zaretskii
2022-10-26 18:03 ` Heime
2022-10-26 18:23 ` Heime
2022-10-26 18:39 ` Eli Zaretskii
2022-10-26 19:14 ` Heime
2022-10-27 5:16 ` Eli Zaretskii
2022-10-27 5:46 ` Heime
2022-10-26 17:50 ` Emanuel Berg
2022-10-25 12:22 ` Jean Louis
2022-10-25 13:10 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-10-26 10:21 ` Daniel Martín
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=83eduuon7o.fsf@gnu.org \
--to=eliz@gnu.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).