#fish_shell — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #fish_shell, aggregated by home.social.
-
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.
-
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.
-
@rl_dane I saw this just before sleep
I tried with #Fish
Fish store history as #YAML
I tweaked the command to make it barely works
Since it's YAML, it's store the timestamps
So, i tried to do an actual #year_in_review
3 hours later, here it is !
https://gitlab.com/pinage404/dotfiles/-/commit/5089def105806afe92684609a004081cf5aa136d
-
@Danathar @[email protected] True! You can be #POSIX compliant and still frustrate any sane *nix user's expectations about how systems work, or do things in non-portable ways. Heck, I use the #fish_shell which doesn't even *try* to be POSIX compliant, but I love working with it anyway and the docs are solid.
I think the real issue is that so much of #Darwin #userland is poorly documented, if at all. That just makes deviations from the norm more painful than necessary IMHO.
-
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
``` -
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.
-
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.
-
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.
-
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.
-
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.
-
Any #StarshipRS users out there? 🖥️ Just build my first preset and tested it accross #powershell, #fish_shell, #bash. Nice to have a consistant promt accross the different shells 😀
https://codeberg.org/pixel-fabian/starship-presets#bielefeld-night
-
@jon same here. longterm #bash_shell and #fish_shell user. Not using #nushell as a daily driver yet but a using it a lot for simple data wrangling pipelines. I love the structured data approach which reduces so much output parsing. And for everything that doesn't have structured output formats I combine it with #jc and `| from json`
-
@jon same here. longterm #bash_shell and #fish_shell user. Not using #nushell as a daily driver yet but a using it a lot for simple data wrangling pipelines. I love the structured data approach which reduces so much output parsing. And for everything that doesn't have structured output formats I combine it with #jc and `| from json`
-
@jon same here. longterm #bash_shell and #fish_shell user. Not using #nushell as a daily driver yet but a using it a lot for simple data wrangling pipelines. I love the structured data approach which reduces so much output parsing. And for everything that doesn't have structured output formats I combine it with #jc and `| from json`
-
Yesterday I created the docker-fish repo to provide Fish 3.7.0 inside Alpine-based container:
docker run --interactive --tty --rm purefish/docker-fish:3.7.0 "fish --version"
-
Rilasciata la shell Fish 3.7.0 con molti miglioramenti
https://www.laseroffice.it/blog/2024/01/19/rilasciata-la-shell-fish-3-7-0-con-molti-miglioramenti/
-
wrote this fish script to run once a day to display the "captain its xday" meme and choose the correct days image.
-
@postmodern #zsh is nifty but overcomplicated. Have you tried #fish_shell yet? It doesn't even pretend to be #POSIX compliant, and does a lot of stuff automagically that you have to really work at in other shells.
It breaks applications that expect to run from inside a #Bourne shell, but I work around that by using zsh as my default shell and then exec-ing fish unless it detects certain conditions that require zsh, which is a very small subset of tools like the #ShellFish #SSH client.
-
@avdi I'm not saying that will be fun, or that there isn't an easier way if we knew what was actually wrong. I'm just sharing my own experiences with the changes in #Homebrew & #macOS, and hoping it solves your issue pragmatically even if not efficiently.
I went through the tortures of the damned getting everything to work right with the #fish_shell (ask me about that sometime), so I empathize. Wish had a better answer, but I hope this helps.