From: Visuwesh <visuweshm@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: larsi@gnus.org, 56008@debbugs.gnu.org
Subject: bug#56008: 29.0.50; image-mode buffer scrolled down automatically
Date: Thu, 16 Jun 2022 22:25:05 +0530 [thread overview]
Message-ID: <87tu8k4kgm.fsf@gmail.com> (raw)
In-Reply-To: <831qvor4l4.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 16 Jun 2022 18:49:27 +0300")
[வியாழன் ஜூன் 16, 2022 18:49] Eli Zaretskii wrote:
>> From: Visuwesh <visuweshm@gmail.com>
>> Cc: Eli Zaretskii <eliz@gnu.org>, 56008@debbugs.gnu.org
>> Date: Thu, 16 Jun 2022 19:44:13 +0530
>>
>> When I tried to dig around in ement.el's source code, I thought it was
>> `save-window-excursion' but that turned out not to be the case AFAIU.
>
> What do you mean by "it was `save-window-excursion'"? what is "it" in
> this case?
I thought the source of the random, unwarranted scrolling could be
`save-window-excursion' since it did come with the following warning,
BEWARE: Most uses of this macro introduce bugs.
E.g. it should not be used to try and prevent some code from opening
a new window, since that window may sometimes appear in another frame,
in which case ‘save-window-excursion’ cannot help.
> And how did you see that this is not the case?
Sorry, but it is close to a year since I looked at the source code. All
I remember is being annoyed by the bug despite removing the
`save-window-excursion' bit willy-nilly.
[ This was all in ement.el's source code if I wasn't clear, BTW. ]
next prev parent reply other threads:[~2022-06-16 16:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 4:01 bug#56008: 29.0.50; image-mode buffer scrolled down automatically Visuwesh
2022-06-16 12:04 ` Lars Ingebrigtsen
2022-06-16 12:19 ` Lars Ingebrigtsen
2022-06-16 13:19 ` Visuwesh
2022-06-16 13:57 ` Eli Zaretskii
2022-06-16 14:05 ` Lars Ingebrigtsen
2022-06-16 14:14 ` Visuwesh
2022-06-16 15:49 ` Eli Zaretskii
2022-06-16 16:55 ` Visuwesh [this message]
2022-06-16 17:11 ` Eli Zaretskii
2022-06-16 17:23 ` Visuwesh
2022-06-16 15:48 ` Eli Zaretskii
2022-06-16 16:58 ` Eli Zaretskii
2022-06-16 17:20 ` Visuwesh
2022-06-16 17:26 ` Eli Zaretskii
2022-06-16 12:52 ` Eli Zaretskii
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=87tu8k4kgm.fsf@gmail.com \
--to=visuweshm@gmail.com \
--cc=56008@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.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.
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).