unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: okamsn@protonmail.com
Cc: stephen.berman@gmx.net, 64547-done@debbugs.gnu.org
Subject: bug#64547: `show-paren-mode` thinks that a paren is offscreen in `M-:` when it isn't
Date: Sat, 15 Jul 2023 10:22:10 +0300	[thread overview]
Message-ID: <838rbhej19.fsf@gnu.org> (raw)
In-Reply-To: <23862422-411d-d519-9b8a-5f12922f1ff2@protonmail.com> (okamsn@protonmail.com)

> Date: Sat, 15 Jul 2023 01:06:54 +0000
> From: okamsn@protonmail.com
> Cc: 64547@debbugs.gnu.org, stephen.berman@gmx.net
> 
> 1) Start `emacs -q` without the new change to paren.el.
> 
> 2) Set `show-paren-context-when-offscreen` to `overlay`.
> 
> 3) In a normal buffer (not the minibuffer), move to the end of a long 
> expression so that the starting parenthesis is no longer on the screen 
> and is not visible.
> 
> 4) See the overlay, as expected.
> 
> 5) Move inside the expression so that the overlay is no longer shown.
> 
> 6) Evaluate the new definition of `show-paren-function`.
> 
> 7) Move back to the end of the long expression.
> 
> 8) See that the overlay is no longer shown.
> 
> 
> I expected to see that the overlay would still be shown for the opening 
> parenthesis that is completely unseen.
> 
> I think that this happens because there is an expression `(not ... (or 
> (< (length part) 4) ...))` which resolves to `nil` when the parenthesis 
> is not visible and not partially visible, from what I can tell.
> 
> Does this make sense?

Thanks, now fixed as you suggested, and closing the bug.





      reply	other threads:[~2023-07-15  7:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-09 19:49 bug#64547: `show-paren-mode` thinks that a paren is offscreen in `M-:` when it isn't Okamsn via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-10 12:15 ` Eli Zaretskii
2023-07-10 13:26   ` Stephen Berman
2023-07-10 14:17     ` Eli Zaretskii
2023-07-14  3:03       ` okamsn--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-14  6:44         ` Eli Zaretskii
2023-07-15  1:06           ` okamsn--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-15  7:22             ` Eli Zaretskii [this message]

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=838rbhej19.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=64547-done@debbugs.gnu.org \
    --cc=okamsn@protonmail.com \
    --cc=stephen.berman@gmx.net \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).