How did you get all the way down here and lose the fact that top level comment is about zsh and finding past commands, and also changing directories? Was it not you that brought up zsh?

And I that brought up bash examples to show how it might be done? We've gone around in circles lads back on the bus.

▲

robenkleene 3 days ago | parent | next [-]

To me, the interesting conversation here is between these three workflows:

1. Recursive directory fuzzy-search

2. Searching history for `cd` commands

3. Zoxide-style matching visited directories

Which are all ways to make it easier to traverse directories.

For my part, the thrust of your argument seemed to be advocating for #1, so that's what I was responding to (since this is a thread on #3, I'm mainly focusing on why you'd use that instead of #1 or #2, but all three are workable).

All of these can be implemented in any of the common shells. I didn't see anyone making a case for a specific shell here, I think the mentions of a specific shell are incidental (e.g., what people happen to use).

	▲	BeetleB 2 days ago \| parent [-]
		Indeed - it's not even an either/or. I have both 1 and 3 as keybindings.

▲

BeetleB 3 days ago | parent | prev [-]

He never said he changed shells - just that he uses zsh history. He was likely using zsh anyway.

▲

jvanderbot 3 days ago | parent [-]

My logic (take it or leave it) is that since zsh is not the default distro nearly anywhere (Kali?), a randomly selected person who might read that advice (and subsequent advice ITT), would likely find "Use ZSH" includes a shell change and therefore more learning curve than "add a few lines to .bashrc".

This is getting off topic, pedantic, and (maybe?) argumentative so I'm calling it quits. Cheers.

	▲	BeetleB 3 days ago \| parent [-]
		I believe the default shell in MacOS is zsh, not bash. So lots of folks use zsh by default.