Feature idea: Pushd and popd

[Mathias-Fuchs]

Hello, it says "feel free to discuss feature ideas", so I'll try to do that.
https://en.wikipedia.org/wiki/Pushd_and_popd are often claimed to be immensely useful and time-saving power features of bash (and others) because they allow users to quickly jump between frequently used directories, easily navigate between multiple directories, and reduce the risk of making mistakes while typing long paths.
Going back to where you're from is one of the most often performed filesystem movements. You're working in one directory, but some task requires you to go somewhere else. You need to get back to your working directory when you're done, etc. Once you get used to thinking in terms of the location stack, you push and pop more than you walk up and down. Maintaining such a location stack might be a great feature in nnn. There just need to be two more commands: one to push the current location on the stack, and the other to go back to the last pushed location.

[N-R-K]

pushd and popd are indeed very useful on shell. But I'm not sure if they make in sense for nnn because nnn already offers 4 context by default, and 8 if you build with O_CTX8=1.

Also we offer going back to the previous dir with - as well (but it's only for "1 level").

[Mathias-Fuchs]

The mental model for a location stack is very different from that of contexts, I think.
The four / eight contexts serve a very different purpose - as their nickname ("workspaces") says, they are for activities that happen in parallel, which you want to keep track of, and between which you need to go back and forth very often. That's great, but a location stack serves a very different purpose: "get me outta here quickly", back to what I was actually working on. No extra mental load required. A location stack can be infinitely deep, but there is only one of them. Location stack is for people who want software to help them to stay focused on just one task instead of several tasks. It's kind of orthogonal to the concept of workspace which helps the user to deal with several tasks at once.
Bash also has the one level - but it only affects the top of the stack - the current directory, and so it doesn't replace pushd/popd.

[N-R-K]

Location stack is for people who want software to help them to stay focused on just one task instead of several tasks. It's kind of orthogonal to the concept of workspace which helps the user to deal with several tasks at once.

Good argument, can't disagree here.

And while this doesn't fulfill all the use-cases for a multi-level context-local stack, I'll just mention that with , you can create a temporary bookmark (and visit it with b,), but it's global and not context-local.

[Mathias-Fuchs]

Yes, that's really cool but they nice thing about a stack is that it can hold a lot of useful information, not just one location, for the user, without increasing their mental load. Do you think there would be a way to integrate that infinitely high stack with the existing context/bookmark system, or would it have to be a separate functionality?

[N-R-K]

Aside from the infinite part (which will be bounded by your system resources), I'd suspect it to be a relatively low effort patch to add it as a separate functionality (it's just a mainly matter of writing a string stack, after all).

But keep in mind that we've recently been very tame with adding new functionalities. So whether jarun would accept it or not is a different question.

[Mathias-Fuchs]

As for merging chances: That's why I wonder if you see a way to integrate it with the workspace context. For example, should each workspace have a stack or should it be a global one? Personally I would find it most useful if it was an alternative. Instead of showing the 4 or 8 contexts, it would show the topmost entries of the stack, just like the dirs command. Sure, the stack itself is trivial to write, it is a char** that grows and shrinks with a xrealloc, and there's some error handling. But the integration with the existing nnn is what requires some thoughts and work.
Actually, this functionality is what I would have thought nnn provides as the default, and I'm really missing it, from an otherwise perfect file manager.
But it seems there might be better ways to integrate it with the existing system, so that it is seen as completing the existing way of doing things instead of a radical alternative. So it's probably better to have each context have its own stack. Upon pushing the context's current directory on top of the stack, a new line would appear below the "1 2 3 4", showing that context's stack. It disappears when the stack is empty. Alternatively, changing directories with a modifier that is not yet used, say p + Return, pushes it and goes there. And so on.

[jarun]

Sorry, no plans.