Bugzilla – Full Text Bug Listing
| Summary: | Inlined rename refactoring should use HOME/END keys better | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Robert Konigsberg <konigsberg> |
| Component: | UI | Assignee: | JDT-UI-Inbox <jdt-ui-inbox> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | daniel_megert, markus.kell.r |
| Version: | 3.3 | ||
| Target Milestone: | 3.3 M7 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
This has been fixed a while ago. Hey, look at that! It's in 3.3M7! Neat!
A small note about what I see in 3.3M7, Daniel.
Using the example
void [fo|o](int x) {
1. I see that CTRL-Shift-R+Home+Home navigates to [|foo and then |void.
2. I see that CTRL-Shift-R+End+End navigates to foo|] and then {|
3. I see that CTRL-Shift-R+End+End+Home navigates (finally) to [|foo (That's great!)
4. However, CTRL-Shift-R+Home+Home+End navigates to {|.
In other words, existing feature is not necessarily symmetric. Shall I open a new bug?
>3. I see that CTRL-Shift-R+End+End+Home navigates (finally) to [|foo (That's
>great!)
That's not what I see when using I20070517-1700. It goes to beginning of void and hence the feature is symmetric.
I downloaded 3.3M7 on my linux workstation and found even different behavior. That is, Home+Home+End navigates to the end of the line and End+End+Home navigates to the start of the line. That's consistent, but not the same as the behavior I saw on my win32 wkstn at home. Sorry I accidentally closed the bug. That's intended. >Home+Home+End navigates to the end of the line and End+End+Home
>navigates to the start of the line.
Maybe you have smart navigation off. If so, Home goes to the beginning and End to the end of a line.
Also note, that the linked mode start/end positions will only be hit if the caret is inside the linked mode.
I just verified that this works as described in 3.3 M7 and 3.3 RC1.
Yeah. OK, thanks for taking the time to review this issue with me. I'm very excited about 3.3. I'll let someone else close it this time. :) . |
When using the new-fangled in-editor Rename refactoring, the Home/End keys should have a special function. In the example below, [ and ] represent the bounding of the rename refactoring, and | represents the cursor. public void [myMe|thod]() { Right now, pressing HOME will move the cursor before the 'p' in public. Similarly, pressing END will move the cursor after the '{'. I'd like to see the following behavior: Pressing HOME will move the cursor before the 'm' in myMethod and pressing END will move the cursor after the 'd' in myMethod. (this should hold true if the cursor is already before the 'm' or after the 'd'. Pressing HOME+HOME or END+END should break this special use of HOME and END. Pressing HOME+END or END+HOME, however, should navigate between both ends of the bounded area.