Bug 500986 - [linked mode] difficulties in shortening a proposed name
Summary: [linked mode] difficulties in shortening a proposed name
Status: REOPENED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 4.7   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Text-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2016-09-07 08:59 EDT by Stephan Herrmann CLA
Modified: 2024-02-09 15:45 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stephan Herrmann CLA 2016-09-07 08:59:46 EDT
Assume you have s.t. like:

   void test(FooBar foobar) {
      |foobar;
   }

* At the caret invoke "Assign statement to new local variable".
* For the variable name you get two proposals "fooBar2" and "bar".
* Edit the initial "fooBar2" to become "foo"
* Hit enter to proceed.
=> "fooBar2" will again be inserted.

After having been surprised by this hundrets of times, meanwhile I know I can use Tab or Ctrl+Enter, both will leave the "foo" as I typed it, but something feels backward to me here. Why should deleting "Bar2" tell the tool that I want that text back on enter? Is it only me or do others see room for improvement, too?

Idea: when ...
- editing in linked mode
- initially buffer content and first proposal are the same
- subsequently the user edits the current linked position
then could this deselect the proposal, so that explicit down-arrow would be needed to insert any of the proposals? I assume that with no proposal selected, enter would behave the way I'd intuitively expect.

Might be a general jface.text issue?
Comment 1 Eclipse Genie CLA 2020-02-28 17:21:48 EST
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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.

--
The automated Eclipse Genie.
Comment 2 Stephan Herrmann CLA 2020-02-28 17:37:17 EST
This still annoys me frequently.
Comment 3 Eclipse Genie CLA 2022-02-18 04:55:25 EST
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.

--
The automated Eclipse Genie.
Comment 4 Eclipse Genie CLA 2024-02-09 15:45:54 EST
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.

--
The automated Eclipse Genie.