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 637946 - Super+1 and Super+2 does not load Home when home is already selected
Super+1 and Super+2 does not load Home when home is already selected
Status: RESOLVED OBSOLETE
Product: gnome-commander
Classification: Other
Component: application
1.4.x
Other Linux
: Normal normal
: 2.0
Assigned To: GNOME Commander maintainer(s)
epiotr
: 740842 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2010-12-24 12:15 UTC by nm
Modified: 2018-08-03 18:03 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description nm 2010-12-24 12:15:52 UTC 
System:

Ubuntu 11.04 Alpha 1
gcmd 1.4 git (2010-12-24)

Reproduce:

1. Stand in any directory and have Home selected in the Dropdown box.
2. Enter Home again in the tab you are standing in.

Result:
The process should enter Home directory again. Instead it does not load anything since home is already selected. The process should be.

Expected result:
Enter selected item when hitting Enter key even if item is already selected.

If Esc key is entered then leave the box and move to last tab used.

Work around:
Enter another item like Smb and then go to Home. Then it will enter the home directory.
Comment 1 Uwe Scholz 2014-01-14 14:25:22 UTC 
I can confirm this behavior. Selecting a directory by using the drop down box and hitting Enter does literally nothing, if the current folder of the tab is a subfolder of the directory in the drop down box.

This applies also to other directories in the drop down box.
Comment 2 Uwe Scholz 2014-11-29 14:14:33 UTC 
*** Bug 740842 has been marked as a duplicate of this bug. ***
Comment 3 GNOME Infrastructure Team 2018-08-03 18:03:17 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-commander/issues/56.