Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BACK vs. PARENT Directory Selection #19

Closed
Bill-MI opened this issue May 29, 2012 · 2 comments
Closed

BACK vs. PARENT Directory Selection #19

Bill-MI opened this issue May 29, 2012 · 2 comments
Assignees

Comments

@Bill-MI
Copy link

Bill-MI commented May 29, 2012

This is surely a feature request. By Nautilus 2.30.1 this little nuisance had not been remedied. The first time I used Nautilus 3 I immediately noticed they finally fixed it. But Caja remains the same as Nautilus 2, of course.

The goal is easy navigation by keyboard-only. Go to a large directory, like /etc. PgDn, Up/DnArrow to rc0.d. Press Enter and you're in /etc/rc0.d.

Navigate back to /etc using either the BACK button or the keyboard equivalent: Alt+LeftArrow. What is now the selected directory? Ideally it would be rc0.d ready to Up/DnArrow in the neighborhood of rc0.d. But it's not... it's reset, inconveniently, way back at the top. This is not a good place to be.

Strangely, the view is at rc0.d but the selection is what counts.

But... the "Open Parent Directory" (keyboard: Ctrl+Up) does take you to /etc with rc0.d nicely selected. This is a poor workaround for general Forward/Back navigation as it keeps adding entries,

I suspect BACK was always supposed to work like PARENT but Nautilus never quite got it right until version 3. Here's hoping Caja can catch up.

@ghost ghost assigned stefano-k Feb 24, 2013
@stefano-k
Copy link
Collaborator

Done 4d06093

@Bill-MI
Copy link
Author

Bill-MI commented Feb 24, 2013

Kudos! The keyboard navigators of the world thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants