From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Lennart Borgman" <lennart.borgman@gmail.com>
Cc: 1166@debbugs.gnu.org
Subject: bug#1166: 23.0.60; Point jumps instead of scrolling in the new line
Date: Sun, 02 Feb 2014 16:06:51 -0800 [thread overview]
Message-ID: <87mwi9cb50.fsf@building.gnus.org> (raw)
In-Reply-To: <e01d8a50810160832k312f39edwe8312f7ee95260cf@mail.gmail.com> (Lennart Borgman's message of "Thu, 16 Oct 2008 17:32:46 +0200")
"Lennart Borgman" <lennart.borgman@gmail.com> writes:
> On Tue, Oct 14, 2008 at 7:57 PM, Lennart Borgman (gmail)
> <lennart.borgman@gmail.com> wrote:
>> I have found a bug where point jumps to a new postion instead of a new
>> line beeing scrolled into the selected window. I am unable to narrow it
>> down, but I can reproduce it (but I am not sure about what makes it
>> happens). Just to get some thoughts I write down what I have seen so far
>> here.
>>
>> The scenario is this:
>> - Point is on the last line in the window.
>> - I press "o" in viper. This opens a line below the current line and
>> puts the point on this line.
>>
>> What I expect to happen is that this new line is scrolled into the
>> window. Sometimes this happens. Sometimes instead point jumps up, maybe
>> 10 lines (I did not count them at all) and the window is not scrolled so
>> the new line is not visible.
>>
>> There are some other ingredients too:
>> - I believe that nxml-mode (or a derivative) must be the major mode.
>> - If I remove nxml-after-change from after-change-functions the bug
>> disappears.
>> - If I try to use edebug it also disappears.
>>
>> Maybe those ingredients also are required, I am not sure since I can't
>> easily reproduce the bug yet:
>> - visual-line-mode.
>>
>> Does anyone have any idea of how to find out what the problem is? In
>> nxml-after-change there is a whole bunch of "save-*" macros. I commented
>> out them all, but the bug still appears. But where is the scrolling done?
>
> It would help if someone could tell me where the scrolling should have
> taken place. To begin with:
>
> - Where in command_loop_1?
> - And then of course a little bit more exact ...
Is this problem still present in Emacs 24?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next prev parent reply other threads:[~2014-02-03 0:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-14 17:57 bug#1166: 23.0.60; Point jumps instead of scrolling in the new line Lennart Borgman (gmail)
2008-10-14 18:29 ` Lennart Borgman (gmail)
2008-10-16 15:32 ` Lennart Borgman
2014-02-03 0:06 ` Lars Ingebrigtsen [this message]
2014-02-03 0:27 ` Lennart Borgman
2014-02-03 5:31 ` 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=87mwi9cb50.fsf@building.gnus.org \
--to=larsi@gnus.org \
--cc=1166@debbugs.gnu.org \
--cc=lennart.borgman@gmail.com \
/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).