The old behaviour was one of the power features of Nautilus for a person that uses keyboard navigation. The new behaviour is dramatically different and frankly doesn't work as well for many use cases.
Lets say I want to quickly navigate to ~/code/myproject/module/__init__.py.
1. I switch to Nautilus which shows my home folder
A. With the old behaviour: c ENTER m ENTER m ENTER __i ENTER
B. With the new behaviour: __init__.py, and it shows me tons of __init__.py located in my home folder and all subdirectories
2. Trying to use the new behaviour and still achieve my goal I try this:
i) module/__init__.py, no hit
ii) module __init__.py, no hit
So, currently I see no way of navigating to the intended file without alot of hassle or reaching for the mouse. A big regression for me.
The old behaviour was one of the power features of Nautilus for a person that uses keyboard navigation. The new behaviour is dramatically different and frankly doesn't work as well for many use cases.
Lets say I want to quickly navigate to ~/code/ myproject/ module/ __init_ _.py.
1. I switch to Nautilus which shows my home folder
A. With the old behaviour: c ENTER m ENTER m ENTER __i ENTER
B. With the new behaviour: __init__.py, and it shows me tons of __init__.py located in my home folder and all subdirectories
2. Trying to use the new behaviour and still achieve my goal I try this:
i) module/__init__.py, no hit
ii) module __init__.py, no hit
So, currently I see no way of navigating to the intended file without alot of hassle or reaching for the mouse. A big regression for me.