unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
* bug#1166: 23.0.60; Point jumps instead of scrolling in the new line
@ 2008-10-14 17:57 Lennart Borgman (gmail)
  2008-10-14 18:29 ` Lennart Borgman (gmail)
  2008-10-16 15:32 ` Lennart Borgman
  0 siblings, 2 replies; 6+ messages in thread
From: Lennart Borgman (gmail) @ 2008-10-14 17:57 UTC (permalink / raw)
  To: emacs-pretest-bug

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'






^ permalink raw reply	[flat|nested] 6+ messages in thread

* bug#1166: 23.0.60; Point jumps instead of scrolling in the new line
  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
  1 sibling, 0 replies; 6+ messages in thread
From: Lennart Borgman (gmail) @ 2008-10-14 18:29 UTC (permalink / raw)
  To: Lennart Borgman (gmail), 1166

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'
> 
> 
> 
> 
> 






^ permalink raw reply	[flat|nested] 6+ messages in thread

* bug#1166: 23.0.60; Point jumps instead of scrolling in the new line
  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
  1 sibling, 1 reply; 6+ messages in thread
From: Lennart Borgman @ 2008-10-16 15:32 UTC (permalink / raw)
  To: emacs-pretest-bug

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






^ permalink raw reply	[flat|nested] 6+ messages in thread

* bug#1166: 23.0.60; Point jumps instead of scrolling in the new line
  2008-10-16 15:32 ` Lennart Borgman
@ 2014-02-03  0:06   ` Lars Ingebrigtsen
  2014-02-03  0:27     ` Lennart Borgman
  0 siblings, 1 reply; 6+ messages in thread
From: Lars Ingebrigtsen @ 2014-02-03  0:06 UTC (permalink / raw)
  To: Lennart Borgman; +Cc: 1166

"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/





^ permalink raw reply	[flat|nested] 6+ messages in thread

* bug#1166: 23.0.60; Point jumps instead of scrolling in the new line
  2014-02-03  0:06   ` Lars Ingebrigtsen
@ 2014-02-03  0:27     ` Lennart Borgman
  2014-02-03  5:31       ` Eli Zaretskii
  0 siblings, 1 reply; 6+ messages in thread
From: Lennart Borgman @ 2014-02-03  0:27 UTC (permalink / raw)
  To: Lars Ingebrigtsen; +Cc: 1166

[-- Attachment #1: Type: text/plain, Size: 2148 bytes --]

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

> "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?
>
>
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.

[-- Attachment #2: Type: text/html, Size: 3721 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* bug#1166: 23.0.60; Point jumps instead of scrolling in the new line
  2014-02-03  0:27     ` Lennart Borgman
@ 2014-02-03  5:31       ` Eli Zaretskii
  0 siblings, 0 replies; 6+ messages in thread
From: Eli Zaretskii @ 2014-02-03  5:31 UTC (permalink / raw)
  To: Lennart Borgman; +Cc: 1166, larsi

> From: Lennart Borgman <lennart.borgman@gmail.com>
> Date: Mon, 3 Feb 2014 01:27:06 +0100
> Cc: 1166@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.





^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2014-02-03  5:31 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2014-02-03  0:27     ` Lennart Borgman
2014-02-03  5:31       ` Eli Zaretskii

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