I've been using #fish_shell more recently, and I really think that fish's abbreviations mechanism is far better than aliases in bash/zsh/others.

https://fishshell.com/docs/current/cmds/abbr.html

Instead of replacing a command with another, you get autocompletion at the command line. This makes copying commands between users or machines way less brittle! You get all the user experience benefits of typing less without creating confusion about what you're actually running.

Kudos to the team behind that decision

Been playing around with #fish_shell lately, and one thing I really like about it compared to bash, is that fish is very big on in-place expansion. Bash provides many shorthands for references to past commands (e.g., !$), or commonly used commands (aliases). However, these shorthands generally don't get expanded until the command is executed.

Conversely, fish's counterparts are expanded in-place on the command line. alt-up modifies the command prompt (vs bash's !$). abbreviations are expanded as soon as you add a whitespace (vs aliases).

It's neat.

It's time for a new blog article!

This time, I present some #tips and tricks for the #FishShell inspired by a recent video from Dreams of Code on Youtube.

https://beeb.li/blog/fish-shell-tips-and-tricks

#fish_shell #shell #FOSS #blog #BlogPost #SmallWeb

I'm currently playing with #Codeium in #Vim, and am finding it interesting. It opens chats using a local browser port, sort of like the #fish_shell help command does. However, I can't find a CLI in #Homebrew (the AI may be hallucinating that there is one) or figure out how to make a whole-codebase query rather than getting context just from the current buffer.

Anyone tried it with Vim yet? How do I ask something like "please summarize what this codebase does" within Vim or at a shell prompt?

For anyone using the #fish_shell, the following #shell_function definition will let you switch to the latest CRuby #chruby knows about. It could be simplified (e.g. setting a function-local variable is mostly for debugging) or use builtins instead of pipes in shells where that matters, but I still find it useful for myself. Maybe you will, too.

```fish
function chruby-latest
set latest (
chruby | tr -d '*' |
pcregrep -o '\bruby-[\d.]+' | tail -1)
chruby $latest
end
```

fish shellのプロンプトにkubectlのContextとNamespaceを表示させてみた
https://dev.classmethod.jp/articles/fish-shell-prompt-kubectl-context-namespace/

#dev_classmethod #Kubernetes #Amazon_EKS #fish_shell

There's been recent discussion about #POSIX & the #bash_shell. Some shells are awesome but don't even pretend to follow the POSIX standards. The #fish_shell is a good example.

Portability can be useful, but context matters too. Why deviate from standards? #LSB excludes #RubyLang but specifies #Perl & #PythonLang. #XDG is needlessly confusing. Distros may deviate from the #Linux #FHS because "reasons."

Goals & targets matter more than portability for its own sake.

https://fishshell.com/docs/current/design.html