feat(app): add history navigation with [ and ], most recent command with -

[tyzbit]

Go Back walks back through the history until at the oldest saved view

Last View switches between the current and previous views like how "cd -" works

EDIT: New description for the features

• Use square brackets [ and ] to navigate the command history back [ and forward ].
• Use the minus/dash key - to switch between the current screen and the last one.

Example
While on the pod screen, type :service and enter. Hitting [ then brings you back to the pod screen. Hitting ] brings you forward in your history to the service screen. Type :ingress and hit enter (you are taken to the Ingresses screen), then hit -, you will go back to the service screen. Hit - again and you will go back to the Ingresses screen.

[tyzbit]

Closes #1786 and #869

Features from these requests not included are:

• It is not possible to go forward again through the history. If you go back, the very last view you were on is removed from the history. - doesn't remove anything from history, just rearranges it. This is no longer true, the history now retains previous commands.
• There is no overview to let you see the history and pick a specific view from it.

This PR implements the most powerful parts of the feature requests. Better navigation and richer history could be added later while keeping this functionality intact.

Supersedes #1090

[KevinGimbel]

Tested the feature locally and I have some questions:

• When I look at containers (Select Pod -> Enter) I cannot go back to the pods with - or b
• Same when using Describe (d)

Is this intended? I assume these "views" are somehow different from the generic Object views (Pod, StatefulSet, Deployment, ...)?

In general I really like this feature! Especially - seems useful! Thank you @tyzbit!

[tyzbit]

I would defer to someone more familiar with the codebase but Views seem to correlate mostly with Kubernetes resources (with the exception of contexts). Maybe the most accurate way to define them is the screens you get when you use a command (e.g. :pods).

When you dive into a resource, you get a trail of breadcrumbs at the bottom.

For demonstration, I went to pods, namespaces and then deployments and then selected a Deployment and hit Enter to go to the Pod, then hit enter again to go to the container, then I checked the cmdHistory:

k9s doesn't add breadcrumb-related navigation to the command history at the present time.

In terms of addressing the difference in expectations, maybe I could update the documentation and help to clarify that Go Back and Last View only work with k8s resources and contexts?

[KevinGimbel]

In terms of addressing the difference in expectations, maybe I could update the documentation and help to clarify that Go Back and Last View only work with k8s resources and contexts?

I think that's a good idea, just to make it clear what to expect from the feature 👍

[tyzbit]

I updated the README.

[KevinGimbel]

Thanks!

One tiny remark:

Your commit changed all * to - for lists - I assume some plugin or editor configuration on your side is making these changes? It makes reviewing the actual code changes hard, and I wonder if future changes will revert this due to different editor configs.

My 2ct would be to revert these style-changes so only the new documentation is added, but I guess @derailed has the final call here :)

[tyzbit]

@KevinGimbel those formatting changes were not intentional, I've changed my settings so it doesn't happen again. While I was at it, I squashed my commits.

[KevinGimbel]

@tyzbit thank you! Looks good to me now. @derailed in my opinion this could be added to the next released :)

[derailed]

@tyzbit Nice work! Good concept. Just a few items to clean up and simplify.

[tyzbit]

Thank you for the great feedback. I'm working on addressing the comments; some planned changes:

• Navigate history with [ and ] instead of B (I prefer this over < and > because it is not necessary to hold shift)
• Add a view to see your history visually and pick a specific point in the history to go to. I think this will aid greatly in training users in using the new features.
• cmdHistory will keep a more accurate history of your commands such as saving the last command used as well as the current command (therefore duplicates are possible and the assumption that history[0] is the current command will be broken, requiring some other updates)

[tyzbit]

I've implemented history navigation via [ and ] and switching to the last command using -. Right now, they're pretty similar because your last view will either be back one in the history or forward one, but I still plan to add a history page that lets you select a specific command out of your history - at that time, lastCommand will be much more useful. I opened #2895 to track that so as of this time, this PR is complete and all previous issues addressed.

[merusso]

@derailed , any thoughts on this PR? Anything else needed to merge this

[saiskee]

As someone that often uses k9s in live demos, this would be a godsend!! @tyzbit Thank you so much for implementing this, and @derailed is there anything that is blocking this from going in?