Bug 101107

Summary:	[navigation] vertical ruler not updating during emacs up/down (ctrl+p/n)
Product:	[Eclipse Project] Platform	Reporter:	Nick Mitchell <nickm>
Component:	Text	Assignee:	Platform-Text-Inbox <platform-text-inbox>
Status:	ASSIGNED ---	QA Contact:
Severity:	minor
Priority:	P3	CC:	daniel_megert
Version:	3.1
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Nick Mitchell

2005-06-21 14:51:20 EDT

If i use the down-arrow key to scroll downwards, the to-do decorations update
when the viewport scrolls, even if I don't let up on the down-arrow key.
However, if I use the emacs ctrl-n equivalent, then the decorations don't update
until i let up on the the "n" key on the keyboard.

this bug does not happen for scrolling up by lines (i.e. ctrl-p)

observed since: 3.1m7, first 3.1 I used

not observed in: 3.0 (first eclipse i used)

expected behavior: ctrl-n should behave as the down-arrow key, and as ctrl-p and
the up arrow key work

Comment 1 Dani Megert

2005-06-21 15:20:40 EDT

*** Bug 101111 has been marked as a duplicate of this bug. ***

Comment 2 Nick Mitchell

2005-06-21 15:49:05 EDT

i was wrong about ctrl-p, it misbehaves just as ctrl-n does

Comment 3 Dani Megert

2008-07-09 09:22:07 EDT

Cannot reproduce in R3.4. If you still see this please reopen and add more detailed steps to reproduce.

Comment 4 Nick Mitchell

2008-07-09 10:42:22 EDT

hi daniel!

i just downloaded 3.4 jee and still see the problem with my existing workspaces. to reproduce, i open up a java file from my workspace, hit ctrl-n or ctrl-p to scroll down or up, and observe that the widgets on the left do not scroll along with the buffer window. as before, when using the arrow keys to scroll up or down, the widgets follow along -- as expected.

Comment 5 Dani Megert

2008-07-09 12:06:13 EDT

OK, see it now. "to-do decorations" sent me into the wrong direction.

Comment 6 Eclipse Webmaster

2019-09-06 15:29:45 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.