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 623124 - Open file/folder location (file properties dialog and file search interface)
Open file/folder location (file properties dialog and file search interface)
Status: RESOLVED DUPLICATE of bug 622789
Product: nautilus
Classification: Core
Component: File Properties Dialog
unspecified
Other Linux
: Normal enhancement
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks: 652944
 
 
Reported: 2010-06-29 11:54 UTC by Savvas Radević
Modified: 2011-12-01 09:09 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Savvas Radević 2010-06-29 11:54:48 UTC
This enhancement is proposed for "File properties dialog" and "File search interface".

* Windows explorer has a nice feature in my opinion, which allows to open the parent folder of a file/folder/link destination. It's located as a button in the  right-click -> Properties dialog.

* Also, while searching (and while browsing), it would be great to have the option "Open file/folder location" and highlight/select the file/folder.

* Finally, when opening a link, it would follow the actual file/folder it links to, open its parent folder and highlight/select the file/folder target.
Comment 1 Savvas Radević 2010-06-29 11:56:35 UTC
Just to mention that there is a nautilus script that "scratches the itch", but can't highlight/select the file/folder: http://pastebin.ubuntu-gr.org/f2c631a90
Comment 2 Savvas Radević 2010-06-29 18:34:56 UTC
This bug could be considered a duplicate of: https://bugzilla.gnome.org/show_bug.cgi?id=622789
..or vice versa, whichever the devs prefer. We ask the same thing actually, but
I didn't know that xenos.d filed the bug. Sorry for the duplicate :)
Comment 3 Savvas Radević 2011-12-01 09:09:24 UTC

*** This bug has been marked as a duplicate of bug 622789 ***