nxes VS fzf

Neat! I'm also working on an extended version of es, it's been hard to work on it consistently, but I've torn out some old code, added a few useful primitives, and implemented a couple nice functions like pushd/popd in the shell itself.

What value does that 10MB bring? 10MB in a vacuum is not a problem with modern storage capacities, but bash is already around 7MB larger than a shell needs to be to supply the benefits it does. Look at shells like ksh, rc, or es (or my own fork nxes) for great examples of significantly smaller shells. Hell, there's barely more utility in bash (~8.44MB) than in oksh (~374KB).

I don't actually see the need to jump around the filesystem that much, but I mostly use this, on many work systems I use the built-in pushd/popd utilities in bash, and on other shells, make use of cd - for quicker backtracking.

Thanks for the link, I'll have to check it out! I've been hacking on an old, public domain shell called es in my spare time and have made some minor progess so far. One of my goals is to eliminate the reliance on a parser generator like Yacc and instead implement my own LALR or LR(1) parser, and was planning on trying to swap out the current Yacc file for something like lemon to start getting a better understanding of what's needed.

In addition, I think bash's `operate-and-get-next` can be very helpful. When you go back through your shell history, you can hit Ctrl+o instead of enter and it will execute the command then put the next one in your history on the command line, and keep track of where you are in your history. This way, you can rerun a bunch of commands by going to the first one and Ctrl+o till you are done. And you can edit those commands and hit Ctrl+o and still go to the next previously run command.

Note: fzf's history search feature breaks this. https://github.com/junegunn/fzf/issues/2399

fzf : https://github.com/junegunn/fzf

Those are the most used aliases in my gitconfig.

"git fza" shows a list of modified/new files in an fzf window, and you can select each file with tab plus arrow keys. When you hit enter, those files are fed into "git add". Needs fzf: https://github.com/junegunn/fzf

"git gone" removes local branches that don't exist on the remote.

"git root" prints out the root of the repo. You can alias it to "cd $(git root)", and zip back to the repo root from a deep directory structure. This one is less useful now for me since I started using zoxide to jump around. https://github.com/ajeetdsouza/zoxide

> my history is so noisy I had to find another way

The fzf search syntax can help, if you become familiar with it. It is also supported in atuin [2].

[1]: https://github.com/junegunn/fzf#search-syntax

[2]: https://docs.atuin.sh/configuration/config/#fuzzy-search-syn...

You call it with `n` and get an interactive fuzzy search for your directories. If you do `n ` instead, it’ll start the find with `` already filled in (and if there’s only one match, jump to it directly). The `ls` is optional but I find that I like having the contents visible as soon as I change a directory.

I’m also including iCloud Drive but excluding the Library directory as that is too noisy. I have a separate `nl` function which searches just inside `~/Library` for when I need it, as well as other specialised `n` functions that search inside specific places that I need a lot.

¹ https://github.com/sharkdp/fd

² https://github.com/junegunn/fzf

View on GitHub

I do find the history pager stuff interesting, but ultimately not of tremendous use for me. I rebound all my history search stuff to use fzf[1] (via a fish plugin for such[2]), and so haven't been aware of the issues

[1] https://github.com/junegunn/fzf

[2] https://github.com/PatrickF1/fzf.fish

You can also use fzf with ripgrep to great effect:

[1]: https://github.com/junegunn/fzf/blob/master/ADVANCED.md#usin...