Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 398230

Summary:	Copy Paste will "rename" multiple files, BUT a normal "rename" will not.
Product:	[Eclipse Project] Platform	Reporter:	Greg Bishop <ggb667>
Component:	IDE	Assignee:	Platform UI Triaged <platform-ui-triaged>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	pwebster
Version:	3.6	Keywords:	helpwanted
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:	stalebug

Description Greg Bishop

2013-01-15 15:09:06 EST

If you copy and paste files you can give each a name in a dialog one at a time.

That WOULD work just fine for multiple files renamed, but you can't rename 
multiple files.  Please just have the rename feature work the same way, prompting
for the name of each file just as copy paste does.

By the Principle_of_least_astonishment
(http://en.wikipedia.org/wiki/Principle_of_least_astonishment)
it would be less astonishing if multiple file rename worked the same way copy paste's dialog does.

How to see the copy paste behavior:  
  1.  Select some files in Package Explorer.
  2.  Paste them.
  3.  It will ask for a new name for each one.

How to see the bug:  
  1.  Select some files.
  2.  You can't pick rename F2 or refator rename. :(

I'm going to say this is a bug, not an enhancement, because you can copy paste the files with the new names as a work around and then delete the old ones.

Possibly Related closed to Bug 208435.

Comment 1 Paul Webster

2013-01-15 15:24:34 EST

I tried it out in my file browser, and that also doesn't enable rename on multiple file selection.

PW

Comment 2 Greg Bishop

2013-06-21 13:41:32 EDT

With respect, your file browser is not an IDE, and the IDE already has this function which is useful working albeit another way.

Comment 3 Lars Vogel

2019-11-27 07:45:42 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.

If the bug is still relevant, please remove the stalebug whiteboard tag.