After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 757180 - Rename popover text entry too narrow
Rename popover text entry too narrow
Status: RESOLVED FIXED
Product: nautilus
Classification: Core
Component: File and Folder Operations
3.18.x
Other Linux
: Normal minor
: 3.18
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 757429 758222 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2015-10-27 12:08 UTC by Davi
Modified: 2015-11-27 08:18 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
files-view: adapt rename entry length (1.98 KB, patch)
2015-11-12 20:42 UTC, Carlos Soriano 		committed Details | Review

Description Davi 2015-10-27 12:08:02 UTC 
Hi,

current popover for renaming files and folders usually only shows a small part of the file name and text entries are not very good on navigation making it hard to make small sparse modifications to large file names. It would be better if the entry in the popover were wider, or even if it were a multi-line text entry, similar to classic inline renaming.

Thanks.
Comment 1 Carlos Soriano 2015-10-27 12:09:09 UTC 
I would like to have it fixed for 3.18
Comment 2 Carlos Soriano 2015-11-12 20:42:10 UTC 
Created attachment 315369 [details] [review]
files-view: adapt rename entry length

We are having some problems given that the rename entry
is kind of small for some file names, and that makes the
rename popover vs inline renaming kind of a problem.
For that, increase the default entry length and adapt
for longer names with a MIN/MAX length.
Comment 3 Carlos Soriano 2015-11-12 20:49:33 UTC 
Attachment 315369 [details] pushed as a5eff66 - files-view: adapt rename entry length
Comment 4 Carlos Soriano 2015-11-12 21:28:26 UTC 
*** Bug 757429 has been marked as a duplicate of this bug. ***
Comment 5 Pavlos Touboulidis 2015-11-27 08:18:19 UTC 
*** Bug 758222 has been marked as a duplicate of this bug. ***