GNU bug report logs - #1166
23.0.60; Point jumps instead of scrolling in the new line

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 1166 in the body.
You can then email your comments to 1166 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> emacsbugs.donarmstrong.com (full text, mbox):

From: "Lennart Borgman (gmail)" <lennart.borgman <at> gmail.com>
To: emacs-pretest-bug <at> gnu.org
Subject: 23.0.60; Point jumps instead of scrolling in the new line
Date: Tue, 14 Oct 2008 19:57:27 +0200

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?


(Note that I am using my patched version right now when investigating
the bugs, but I do not think it matters here.)

In GNU Emacs 23.0.60.1 (i386-mingw-nt5.1.2600)
 of 2008-10-14 (patched)
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (3.4) --cflags -Ic:/g/include'

Message #10 received at 1166 <at> emacsbugs.donarmstrong.com (full text, mbox):

From: "Lennart Borgman (gmail)" <lennart.borgman <at> gmail.com>
To: "Lennart Borgman (gmail)" <lennart.borgman <at> gmail.com>,
        1166 <at> debbugs.gnu.org
Subject: Re: bug#1166: 23.0.60; Point jumps instead of scrolling in the new
 line
Date: Tue, 14 Oct 2008 20:29:20 +0200

Lennart Borgman (gmail) 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.

Yes, visual-line-mode is required too. More precisely only `word-wrap'
needs to be set to t for the bug to appear.

> 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?
> 
> 
> (Note that I am using my patched version right now when investigating
> the bugs, but I do not think it matters here.)
> 
> In GNU Emacs 23.0.60.1 (i386-mingw-nt5.1.2600)
>  of 2008-10-14 (patched)
> Windowing system distributor `Microsoft Corp.', version 5.1.2600
> configured using `configure --with-gcc (3.4) --cflags -Ic:/g/include'
> 
> 
> 
> 
> 

Message #15 received at submit <at> emacsbugs.donarmstrong.com (full text, mbox):

From: "Lennart Borgman" <lennart.borgman <at> gmail.com>
To: emacs-pretest-bug <at> gnu.org
Subject: Re: bug#1166: 23.0.60; Point jumps instead of scrolling in the new line
Date: Thu, 16 Oct 2008 17:32:46 +0200

On Tue, Oct 14, 2008 at 7:57 PM, Lennart Borgman (gmail)
<lennart.borgman <at> 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 ...

View this message in rfc822 format

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: "Lennart Borgman" <lennart.borgman <at> gmail.com>
Cc: 1166 <at> 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

"Lennart Borgman" <lennart.borgman <at> gmail.com> writes:

> On Tue, Oct 14, 2008 at 7:57 PM, Lennart Borgman (gmail)
> <lennart.borgman <at> 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/

Message #22 received at 1166 <at> debbugs.gnu.org (full text, mbox):

From: Lennart Borgman <lennart.borgman <at> gmail.com>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 1166 <at> debbugs.gnu.org
Subject: Re: bug#1166: 23.0.60;
 Point jumps instead of scrolling in the new line
Date: Mon, 3 Feb 2014 01:27:06 +0100

[Message part 1 (text/plain, inline)]

On Mon, Feb 3, 2014 at 1:06 AM, Lars Ingebrigtsen <larsi <at> gnus.org> wrote:

> "Lennart Borgman" <lennart.borgman <at> gmail.com> writes:
>
> > On Tue, Oct 14, 2008 at 7:57 PM, Lennart Borgman (gmail)
> > <lennart.borgman <at> 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?
>
>
Unfortunately I have no idea. I am still using my old patched version of
Emacs. And I do not have time to upgrade since that would require either
patching again or getting the patches inside Emacs. Both alternatives takes
more time than I can afford now.

[Message part 2 (text/html, inline)]

Message #25 received at 1166 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Lennart Borgman <lennart.borgman <at> gmail.com>
Cc: 1166 <at> debbugs.gnu.org, larsi <at> gnus.org
Subject: Re: bug#1166: 23.0.60;
 Point jumps instead of scrolling in the new line
Date: Mon, 03 Feb 2014 07:31:24 +0200

> From: Lennart Borgman <lennart.borgman <at> gmail.com>
> Date: Mon, 3 Feb 2014 01:27:06 +0100
> Cc: 1166 <at> debbugs.gnu.org
> 
> > Is this problem still present in Emacs 24?
> >
> >
> Unfortunately I have no idea. I am still using my old patched version of
> Emacs. And I do not have time to upgrade since that would require either
> patching again or getting the patches inside Emacs. Both alternatives takes
> more time than I can afford now.

Why can't you check this in one of the available snapshot binaries?
Or show a recipe starting from "emacs -Q", so that someone else could
try this in the current development version?

If the problem only happens in your patched Emacs, then I don't think
we should keep it in the Emacs bug tracker.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.