Bug 260242

Summary:	[navigation] Provide a shortcut to focus on the first visible line
Product:	[Eclipse Project] Platform	Reporter:	Mohsen Saboorian <mohsens>
Component:	Text	Assignee:	Platform-Text-Inbox <platform-text-inbox>
Status:	ASSIGNED ---	QA Contact:
Severity:	enhancement
Priority:	P5	CC:	daniel_megert
Version:	3.5	Keywords:	helpwanted
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Mohsen Saboorian

2009-01-07 07:24:46 EST

This is very common that one uses mouse to scroll up/down a Java code to see how the things are going on. The cursor may be on a line which is not currently visible. As soon as the user presses any key, the screen is scrolled to where the cursor is.

Please provide a short-key to focus the cursor on the first line of the visible code.

Comment 1 Dani Megert

2009-01-09 03:16:51 EST

You can do this using Arrow Left and/or Arrow Right. Adding a special command seems overkill and there doesn't seem to be much interest (no request for this for more than seven years). We won't work on this.

If you really want this I suggest you attach a good quality.

Comment 2 Mohsen Saboorian

2009-01-09 03:36:56 EST

(In reply to comment #1)
> You can do this using Arrow Left and/or Arrow Right. Adding a special command
> seems overkill and there doesn't seem to be much interest (no request for this
> for more than seven years). We won't work on this.

Arrow Left/Right actually scrolls to the location cursor already exists. I want to focus somewhere in the current visible page. OK, then I hope more people vote for this ;)

> If you really want this I suggest you attach a good quality.
Good quality code you mean?

Comment 3 Dani Megert

2009-01-09 03:39:13 EST

>Arrow Left/Right actually scrolls to the location cursor already exists. 
Well, yes if it is in the viewport but I thought you want this for cases where the caret is outside. Anyway.

>Good quality code you mean?
I meant a good quality patch.

Comment 4 Eclipse Webmaster

2019-09-06 16:04:20 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.