@jdx's recommendations: Fish & Starship

[rsyring]

I happened across an older version of the Tips & Tricks page that has some recommendations from @jdx regarding his shell tools. In particular, he recommended:

• Fish shell: I'd tried it once before but had some problems and decided to punt. Given this recommendation, I've picked it up again, spent the day tooling around while watching the football, and believe this will be my new shell.
• Starship: cross-shell customizable prompt (which mise will install/manage)

And in relatively short order, I have an amazingly better and more useful cli experience:

My Starship config:

# Notes:
#
# starship print-config > ~/.config/starship-print-config.toml
#
# colors: https://i.stack.imgur.com/KTSQa.png


# format = ' $git_branch$status$cmd_duration$fill$python$all $directory$character'
format = ' $status$cmd_duration${env_var.VENV_NAME}$directory$git_branch$fill$python$all $character'

[cmd_duration]
min_time = 2000
format = "[$duration]($style) "
style = "fg:69 bold"

[directory]
# truncate_to_repo = false

[env_var.VENV_NAME]
variable = 'VIRTUAL_ENV_NAME'
format = '[\($env_value\)]($style) '
style = "yellow bold"

[fill]
style = "bold black"
symbol = "#"

[git_branch]
format = "[$symbol$branch(:$remote_branch)]($style) "

[git_state]
disabled = true

[git_status]
disabled = true

[nodejs]
format = "[$symbol($version )]($style)"
version_format = "${raw}"
symbol = "❯ js "

[python]
format = '[${symbol}${pyenv_prefix}(${version} )]($style)'
version_format = "${raw}"
symbol = "❯ py "

[status]
format = "[$symbol$status]($style) "
symbol = "rc "
disabled = false
style = "bold fg:196"

And my Fish config:

if status is-interactive
    # Commands to run in interactive sessions can go here

    /usr/bin/mise activate fish | source

    ~/.local/share/mise/installs/starship/latest/bin/starship init fish | source
end

# Facilitates showing just the venv name in the prompt.  I wanted that and the Python version in separate places.
function __venv_name_eval --on-event fish_prompt
    if test -n "$VIRTUAL_ENV"
        set --global --export VIRTUAL_ENV_NAME (basename "$VIRTUAL_ENV")
    else
        set --erase VIRTUAL_ENV_NAME
    end
end

I plan to check out just a few more tools:

• Directory traversal: z or zoxide
• fzf: command line fuzzy finder
• oh-my-fish
• fisher

Although, I think one of the benefits of my current setup is that its pretty simple so I'm not planning to rush into anything.

HTH.

[roele]

There is the fzf.fish plugin you can install via fisher. It has dependencies on fzf (fd, bat) but is highly customizable and comes with good defaults. It is missing z functionality in general but i just implemented that myself (see PatrickF1/fzf.fish#231).

[jdx]

check out zoxide for that (which Randy mentioned). I personally have struggled getting it into my workflow but from testing it does seem like a good z replacement that I wish I could get in the habit of using.

Maybe I'll give it another go.

[rsyring]

Interestingly, the one issue I had getting these fish plugins to work was that I wanted to use mise to manage their installations (using asdf plugins). But, those tools aren't on the path yet when the plugins init. They look for the binaries, don't find them, and exit.

I "solved" this by just symlinking the latest version of those tools to ~/bin/. Not sure it was the best solution but I had spent the better part of the day getting all this working and wanted to move on to...sleep. :)

[jdx]

btw the reason I took that section out was because the aliases stuff is actually already mentioned in other parts of the docs and I felt the starship/fish stuff wasn't very related to mise. That said, they are great tools and I'm glad you've found some use from them!

I'm glad you posted this