From: Eli Zaretskii <eliz@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: larsi@gnus.org, esabof@gmail.com, 14582@debbugs.gnu.org
Subject: bug#14582: 24.3.50.1; Strange overlay behavior, when window-start is inside an overlay.
Date: Wed, 09 Feb 2022 15:47:51 +0200 [thread overview]
Message-ID: <83wni4up6g.fsf@gnu.org> (raw)
In-Reply-To: <875ypor90e.fsf@web.de> (message from Michael Heerdegen on Wed, 09 Feb 2022 04:53:05 +0100)
> From: Michael Heerdegen <michael_heerdegen@web.de>
> Cc: larsi@gnus.org, esabof@gmail.com, 14582@debbugs.gnu.org
> Date: Wed, 09 Feb 2022 04:53:05 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Neither do I, so there's something else at work here.
>
> I failed to find a recipe in half an hour and gave up for now - instead
> I found one for a very similar case of unexpected auto-scrolling that
> only appears when the new feature is turned on. Also seems to depend on
> the buffer contents. Maybe it is related and a fix fixes the other
> thing, too.
>
> emacs -Q
> 1 C-h i
> 2 move point to the beginning of one of the last visible lines.
> no scrolling happens (good).
> 3 M-: (setq make-window-start-visible t) RET => *info* buffer scrolled
>
> If you scroll back so that (point-min) becomes visible and repeat step
> 2 any activation of the minibuffer, e.g. just hitting M-: or C-x k,
> scrolls the *info* buffer.
>
> Doesn't happen in C-h n. Dunno what makes the difference - the fact
> that *info* is narrowed or that different fonts are used.
>
> Ah - wait, now I can reproduce the other thing, too:
>
> M-:
> (progn
> (setq-default display-time-interval 1.)
> (setq display-time-format "%H:%M:%S")
> (setq-default make-window-start-visible t)
> (display-time-mode +1))
> RET
> C-h i
> [down] [down] not too fast ... until it scrolls
You asked for it. Info buffers have a 'display' property whose value
is a string at the beginning of each node, and that 'display' property
makes the window's start point invisible. So whenever Emacs can make
the window-start visible, it does.
IOW, here you have one example why the default way of handling
"hidden" window-start point is sometimes exactly what we want.
Bottom line: I advise against making this the default.
next prev parent reply other threads:[~2022-02-09 13:47 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-09 9:13 bug#14582: 24.3.50.1; Strange overlay behavior, when window-start is inside an overlay E Sabof
2013-06-09 17:06 ` Eli Zaretskii
2013-06-09 17:37 ` E Sabof
2013-06-09 17:52 ` Eli Zaretskii
2013-06-09 18:16 ` E Sabof
2013-06-09 18:25 ` Eli Zaretskii
2013-06-09 18:40 ` E Sabof
2013-06-09 18:49 ` E Sabof
2022-01-30 21:37 ` Lars Ingebrigtsen
2022-01-31 0:36 ` Michael Heerdegen
2022-01-31 14:57 ` Eli Zaretskii
2022-01-31 18:42 ` Michael Heerdegen
2022-01-31 19:08 ` Eli Zaretskii
2022-02-01 3:03 ` Michael Heerdegen
2022-02-01 18:18 ` Eli Zaretskii
2022-02-02 1:12 ` Michael Heerdegen
2022-02-02 3:34 ` Eli Zaretskii
2022-02-02 4:02 ` Michael Heerdegen
2022-02-02 12:31 ` Eli Zaretskii
2022-02-03 17:40 ` Eli Zaretskii
2022-02-04 1:37 ` Michael Heerdegen
2022-02-04 13:56 ` Eli Zaretskii
2022-02-06 2:54 ` Michael Heerdegen
2022-02-06 10:28 ` Eli Zaretskii
2022-02-08 0:29 ` Michael Heerdegen
2022-02-08 3:34 ` Eli Zaretskii
2022-02-08 4:05 ` Michael Heerdegen
2022-02-08 12:23 ` Eli Zaretskii
2022-02-09 0:20 ` Michael Heerdegen
2022-02-09 3:53 ` Michael Heerdegen
2022-02-09 13:47 ` Eli Zaretskii [this message]
2022-02-10 1:07 ` Michael Heerdegen
2022-02-10 6:15 ` Eli Zaretskii
2022-02-11 4:42 ` Michael Heerdegen
2022-02-11 8:46 ` Eli Zaretskii
2022-02-12 0:25 ` Michael Heerdegen
2022-02-12 7:28 ` Eli Zaretskii
2022-02-12 22:53 ` Michael Heerdegen
2022-02-13 11:43 ` Eli Zaretskii
2022-02-27 3:54 ` Michael Heerdegen
2022-02-27 8:08 ` Eli Zaretskii
2022-02-27 23:19 ` Michael Heerdegen
2022-02-28 13:10 ` Eli Zaretskii
2022-01-31 15:30 ` Lars Ingebrigtsen
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=83wni4up6g.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=14582@debbugs.gnu.org \
--cc=esabof@gmail.com \
--cc=larsi@gnus.org \
--cc=michael_heerdegen@web.de \
/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).