-
Notifications
You must be signed in to change notification settings - Fork 643
feat: backward/forward #230
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
Conversation
|
Why does backward/forward only work for cd? I think it should be expanded to apply to all navigation, and this wouldn't affect the current behavior of cd, just widen the scope. |
For practical reason. Just like in text editor, you only need backward/forward when you make a jump (imagine how it would be if you go backward and the cursor only moves up one line). |
|
I haven't seen any file managers that implement forward/backward only for the "jump"... I can't imagine what harm reducing the granularity of operations would cause; on the contrary, if the granularity is too large, it would be limiting when users actually need it. |
|
I also use other file manager and I think this is the better way to do backward/forward. Imagine if I'm in folder In the same situation, with this implementation, when I'm in Someone would argue "what if I want to go back one folder?", just use |
|
Have you ever considered: In the current directory
|
|
I don't run into that situation often but I can see where you're coming from. How about this: keep the current implementation and add an So when you're at |
|
On second thought, that kind of functionality may better be done in a bookmark or jump list plugin. Ok, I'll change the behavior to that of normal file manager. |
|
I made some changes, removed the unnecessary |
|
Oh, that's a clever way to guard against backward/forward pushing to stack. It looks fine to me. |
Backward/forward only works with big jump (cd, zoxide...).This pull request also includes an improvement of #228.Recording.2023-09-30.173444.mp4