miniforge VS fzf

Nope they don't use venv for any of the oobabooga# variants nor is it recommended for the git version. I'm using https://github.com/conda-forge/miniforge#mambaforge-pypy3 (better version of the recommended conda) for the git variant. The oobabooga* variant uses micro/miniconda (I suck with names) which you can easily drop into with cmd_?something? and does it all internally. Like whoever built that whole environment setup for the _windows/linux/mac did a great job.

wget https://github.com/conda-forge/miniforge/releases/latest/download/Miniforge3-Linux-aarch64.sh .

Mambaforge!

Just to further clarify: you don't need mamba to avoid the Anaconda distribution. The place you get mambaforge also supplies (and originally supplied) miniforge, which is miniconda with conda-forge set as the default channel. All the *forge installers do in this regard is automatically set conda-forge as the default (and only) channel, which is something one can do manually with miniconda.

I'd recommend using miniforge if you're comfortable with CLIs, otherwise https://www.anaconda.com/.

Tip 1: To use less of your Codespaces resources start with a smaller image like Miniconda or Miniforge and install only what you need.

miniforge, no need to deal with conda environments anymore. https://github.com/conda-forge/miniforge

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...