9 ms·
Fish – A friendly interactive shell
- nicechianti 3y ago[dead]
- toastal 3y ago[flagged]
- 21eleven 3y agoWhat I like about fish is that it provides a lot of nice-to-have ergonomic features from the get go without having to install plugins. I add starship.rs to it and fzf integration but that's it.
- deleted 3y ago[deleted]
- Kiro 3y agoWhy do you need starship.rs?
- dinckelman 3y agoYou don't need it. But it's just a really good, no-bullshit, customizable prompt, and you can use it with basically any shell you like, drop-in
- Kiro 3y agoI think I misunderstand what "prompt" is referring to here. What is it?
- Zizizizz 3y agohttps://starship.rs/ https://starship.rs/ A shell theme
- dinckelman 3y agoWhen you open a new shell, by default it'll say something like `user@hostname: cursor`. Starship lets you change that to whatever you want, but out of the box it hides unnecessary information, and shows you stuff like the your language and package versions, if you're navigated into a git repo, for example. Take a look at it yourself, there's a lot you can do
- hiAndrewQuinn 3y agoYeah. I love the default starship and install it on every shell I use, currently PowerShell + fish + bash. It shows me all kinds of useful info like which k8s cluster I'm logged into, which AWS/Azure/GCP account, whether the current directory has uncommitted git changes...
- mattgreenrocks 3y agoDoes it have async git checks yet?
- 21eleven 3y agoBased on my experience opening a clone of the nixpkgs repo the other day... I don't think so :)
- wodenokoto 3y agoWouldn’t that also be the two things one would do in bash?
- 21eleven 3y agoThis is true. However I was calling out, wrt fish, the only two additional "plugin" type things I add in order to have a comfortable shell environment. Fish conveniently provides history based autocomplete so I don't need to setup some plugin for that.
- woleium 3y agoI used fish for a while (and really enjoyed it, it's a great shell), but it's formatting is too inconsistent with bash for me. I found myself dropping back to zsh so often to write documentation or run a playbook that I switched back. If you often share shell code with others it may be to big of a leap for you.
- csmattryder 3y agoIf you're running a script, you can use edc/bass to run it from a fish shell. Fisher is one of the first things I install after fish, then bass, z and a few other helper plugins. https://github.com/edc/bass https://github.com/edc/bass https://github.com/jorgebucaran/fisher https://github.com/jorgebucaran/fisher
- cedilla 3y agoI use fish since they relented and allowed to use && and || instead of ;or and ;and. Still, I always script with bash (or POSIX sh for certain things). I can't recommend that split enough. Also, I can't speak highly enough of shellcheck[1], it's a lifesaver especially when you target POSIX. 1: https://www.shellcheck.net/ https://www.shellcheck.net/
- keepamovin 3y agoI'm there with you on that.
- girishso 3y agoTried fish a couple of times, it's really good, many zsh plugins are created to replicate features of fish. But it's not my default shell, because I need to run bash shell scripts and I didn't find any way to do it in fish. So I am stuck with my slow zsh.
- keepamovin 3y agoMaybe ask ChatGPT4 to translate them?
- notnmeyer 3y agothis shouldn’t be necessary and is probably fairly error prone. using one shell doesn’t mean you can run stuff in another. if someone is saying they can’t run a bash script when they’re invoking bash from fish the most likely thing is they’re doing something wrong.
- pxc 3y agoI asked an LLM to translate a bash script to fish once and it just changed the shebang line... cracked me up. Edited to add: There's a program out there for translating bash to fish called babelfish. It's pretty good but not complete, so it won't work for all scripts. Worth checking out, though: https://github.com/bouk/babelfish https://github.com/bouk/babelfish
- keepamovin 3y agoYeah, I've seen those stuck in loops where they don't see an obvious mistake.
- st3fan 3y agoYou don't have to translate them. Just stick `#!/usr/bin/env bash` on top. It is totally fine to use fish as your "terminal shell" and default to Bash for scripting for things like automation, etc. I've been doing this for a decade. I will also add that Fish is so good by default that I barely have any config.
- 3y ago
- dinckelman 3y agoI've used fish for about 5 years now, and I don't really wanna go back. Out of the box, without any addons at all, it does everything my old zsh setups did, with a package manager and plugins. The only change I've made to it was spacefish (now starship.rs)
- beebmam 3y agoDoes it have support for reverse search yet? Not interested in auto complete.
- bin_bash 3y agoyou just push ctrl-r just like in zsh
- srjilarious 3y agoI end up installing mcfly (https://github.com/cantino/mcfly https://github.com/cantino/mcfly) in all my shells, and it works great in fish as well.
- tipsytoad 3y agoI like https://github.com/PatrickF1/fzf.fish https://github.com/PatrickF1/fzf.fish Can also do cool stuff like search for a file to open in $EDITOR and searching git log
- deleted 3y ago[deleted]
- buildbot 3y agoI’ve used fish for nearly a decade now, it’s awesome. The autocomplete works for so many things you don’t expect! Command line arguments! Remote path completion! Git! It’s something I install basically on everything machine I can. The history based autocomplete is so useful for keeping track of and refinding those less used complex commands that you have not saved in a function yet.
- dizhn 3y agoI love their tagline. Very funny. I used it for a while and liked it enough but their development strategy is explicitly against having configurable options. A few things nagged me and there was no way to change the behavior so I switched to zsh and made it work like fish, but the way I like it instead. For me this was a good decision and I recommend it. (I am not a fan of oh-my-zsh or plugin managers etc either)
- em-bee 3y agocan you elaborate on what nagged you? i am just curious, not critical. i use fish, zsh and now also elvish. the main thing for me is autosuggestion and getting history with uparrow. zsh has a module for autosuggestion. elvish has uparrow history (but only matches at the start). so fish still wins over the others. elvish comes second because typing a command and hitting uparrow once is almost like autosuggestion. but i could not find a way to get that in zsh. i also prefer the way fish and elvish handle blocks over the traditional sh-shell style.
- JNRowe 3y agoI'm unsure what specific behaviour you want from zsh and the up key, but it provides more than one up-line-*¹² function out of the box. Also, you can add any behaviour you wish with a custom zle function. That said, I understand some people prefer to just use something with the default settings. ¹ https://zsh.sourceforge.io/Doc/Release/Zsh-Line-Editor.html#index-up_002dline_002dor_002dhistory https://zsh.sourceforge.io/Doc/Release/Zsh-Line-Editor.html#... ² https://zsh.sourceforge.io/Doc/Release/Zsh-Line-Editor.html#index-up_002dline_002dor_002dsearch https://zsh.sourceforge.io/Doc/Release/Zsh-Line-Editor.html#...
- em-bee 3y agoto explain the up key: prompt> some-word[up key] will search for some-word in the history. this feature helps because in 90% of cases i can type some-word and have autosuggestion show me the right command, so i just need to hit right arrow and enter to run it. but, if the suggestion is wrong, i can instead hit up arrow and search for a another history entry. in zsh currently, i can get autosuggestions, but if the suggestions is wrong, i have to type ctrl-A and retype some-word in order to search the history. i want to be able to do that without retyping, the way it is done in fish. elvish only has the uparrop feature which gets me there halfway, i can type something, and then hit uparrow to find a matching command. in most cases the first hit is the one i want, but if not i keep searching. i prefer to also have the autosuggestion because often i don't remember that i have a similar command already, and the autosuggestion provides that hint. together these are the two most useful features that i want from a shell.
- gfiorav 3y agoI loved fish for about 5 years. My only gripe is that going back to Mac it wouldn’t play nice with the terminal color scheme, or the dark mode switch. Anyone found a way around that?
- innocentoldguy 3y agoI use iTerm2 instead of the default Terminal app. In iTerm2, you can change the impossible-to-see blue and red to more reasonable values (or do what I do and use the Dracula Pro Themes).
- memco 3y agoFish has some options for that via `fish_config`: https://fishshell.com/docs/current/cmds/fish_config.html https://fishshell.com/docs/current/cmds/fish_config.html. You can use the browser tool or `fish_config theme ...` to find colors that work better.
- rany_ 3y agoThe biggest screw up is that fish is not bash compatible. I'm just too used to bash and am not willing to change that because there are corporate systems where I only have access to bash and nothing else; and cannot install fish. It will just be hurtful to need to keep switching between different scripting languages; I will never be able to do so comfortably and with muscle memory.
- erikpukinskis 3y agoI don’t follow… could you put #!/bin/bash at the top of your scripts, and still use it for scripting, but then use fish as your interactive shell?
- mcpackieh 3y agoI think this is what most fish users do. I suspect that failing to understand this is possible, due to not understanding how shebang scripts are executed by the kernel, is a major reason why bash remains popular for interactive use.
- joseph 3y agoIt's not that. We don't want to switch shell syntax between workstation and server, for example. The fish users I've known moved very slowly when they had to hop on a server, or build a new container image where it involved a 'docker run' into the shell to test it out. If you know bash or sh well enough to do those things quickly then there is no incentive to use fish.
- mcpackieh 3y agoBut `docker run` is the same in every shell. The only things that really change is the syntax for looping over files, advanced globing, things like that. Control-R, tab completion etc all works more or less the same with some minor quirky differences, but nothing that would slow somebody down. Context: I used bash for about 5 years, zsh for the next 10 before switching to fish.
- pacifika 3y agoI had to abandon the last time I tried fish because it’s not compatible with my export PATH declarations from tooling in bash/zsh, any tips?
- artemisart 3y agoJust rewrite them once with fish_add_path? https://fishshell.com/docs/current/tutorial.html#path https://fishshell.com/docs/current/tutorial.html#path Or maybe use https://github.com/edc/bass https://github.com/edc/bass
- PufPufPuf 3y agoYou can source bash files (like .bashrc) using the plugin "bass". You can also launch fish using a bash file, just export the variables and run fish as the last command. I personally just put what path modifications I need in .profile and have fish as my login shell.
- bin_bash 3y agoOK so if you're new to fish you should understand universal variables since it's a concept that bash/zsh does not have and it's actually pretty great. When people first try out fish they want to add their global env vars and PATH configuration to ~/.config/fish/config.fish. You can absolutely do this similar to how you do it in ~/.bashrc. However, it's not idiomatic and once you get used to universal variables, you'll see that it's a lot of yak shaving you really just don't need editing config.fish. Instead, if you want to permanently set an env var across the current session and all new sessions, run: `set -Ux MY_ENV_VAR 1` (set a universal variable, and export it to subprocesses) That will put it into a machine-readable file ~/.config/fish/fish_variables. You can open it if you want but this way you don't need to source your rc files, open a new shell, or even open your editor. For PATH, just run: `fish_add_path ~/my-new-bin`. It uses universal variables by default. For some reason I avoided universal variables as much as possible for years using fish and now I think that was really silly.
- Flimm 3y agoI think later versions of Fish do support export statements. This line of code works with Fish, as well as Bash and Zsh: export PATH="$PATH:$HOME/foobar/"
- madspindel 3y agoWhy use this over nushell?
- em-bee 3y agoi can't find anything about history handling in nushell. it's one of the key features of fish
- microflash 3y agoThey recently added sqlite backed history. You can also use atuin[1] for more advanced usecases. [1]: https://github.com/atuinsh/atuin https://github.com/atuinsh/atuin
- bin_bash 3y agoThey're really completely different. Fish is mostly about having features that help you enter a command (history, error checking, completions, etc). Once you execute something, it really behaves the same as bash/zsh. Nushell is really more about command output (my understanding, I haven't used it heavily). With Nushell you can do things like parse TOML files right in your shell: open Cargo.toml | get package.version Nushell understands the structure of data but fish is like bash/zsh in that it just deals with streams of text. Nushell can even interact directly with sqlite databases which is very cool. I think if you're just looking for a simple shell that behaves a lot like bash/zsh, use fish. I think Nushell is more targeted to people that want to use its powerful data pipeline features—or are generally interested in a bigger departure from bash/zsh. Personally I prefer fish, but I should start using Nushell more since it could definitely help with some tasks. I probably would just run Nushell when I need it though, I don't see myself running chsh to switch over.
- foobarqux 3y agoI don't use fish but it does have one great feature that I'm surprised hasn't been replicated in zsh: automatic completions derived from man pages. So you get at least basic flag completions for basically every program automatically.
- pxc 3y agoI've been using Fish as my login shell for more than a decade now. Unlike many other commenters here, I also use it for scripting. For simple stuff, it's way nicer for writing scripts because the language just has has fewer gotchas than bash. If you're just reading instructions online, translating between examples given in bash and fish is trivial. I see people talk about that being an issue for them and I don't understand it; it's literally never given me trouble.
- karl42 3y agoThe one thing that keeps me from using it more often for scripting is the lack of a fail-on-error mode (similar to `set -e` on bash). I know it is hard to get this to behave well in all cases (e.g. pipefail) but I don't want to do much scripting without it.
- pxc 3y agoThe other ones that annoy me are shell redirection from fish functions and some job control issues, which I'm hoping will both be fixed when job control is rearchitected as part of the ongoing Rust port. I still use bash in CI, and for Linux scripts that I distribute to others. For macOS automation, I use zsh since it's the default nowadays. My fish scripting is mostly for personal use and occasionally little wrappers on servers that I own. Sometimes I'll share a bit of fish code with other fish users at work, too. Fail-on-error would be nice and help make the case for using fish in more places. At organizations where no one really knows bash that well anyway, fish would actually be nicer for scripting than bash if it had just a few more goodies like that imo.
- assbuttbuttass 3y agoI tried zsh at some point, but I got the impression that it's basically the same as bash out of the box, and you need to spend time customizing it to see the benefits. I don't want to spend time customizing my shell, I want it to work out of the box. Fish is noticeably better than bash out of the box, with absolutely no customization. Magic autocomplete is life-changing.
- istjohn 3y agoI quit fish because I missed being able to `sudo !!` to rerun the previous command with sudo. There's an alternative way to do it (something like up arrow, ctrl-i, "sudo", enter), but I can never remember it when I need it, which is not often enough to stay in my head, but often enough to be come quite annoying.
- 7839284023 3y agoI hope that you are joking since you just have to press `Alt` + `S` to rerun the previous command with sudo in fish-shell: > `Alt` + `S` Prepends sudo to the current commandline. If the commandline is empty, prepend sudo to the last commandline. https://fishshell.com/docs/current/interactive.html#shared-bindings https://fishshell.com/docs/current/interactive.html#shared-b...
- JNRowe 3y agoThat is a recent(-ish) addition¹, arriving in 3.1. Your interpretation of recent may be a different length to mine, but one Debian release in this instance ;) ¹ https://github.com/fish-shell/fish-shell/pull/6140 https://github.com/fish-shell/fish-shell/pull/6140
- winter_blue 3y agoI guess he wasn't aware. I use fish, and I'm learning this now too. I probably really should give the fish docs a read-through, as I imagine it could significantly improve my shell efficiency.
- istjohn 3y agoGlad to hear that's changed. There were strident statements from the developer on Github last time I researched it to the effect that implementing '!'-style history expansion was contrary to the fish philosophy and that people just need to learn the fish-y way. Looking back it, I probably could have fixed the issue for myself by setting up vi-mode in fish, but I didn't come across that option at the time.
- rileymichael 3y ago
- lacrimacida 3y agoFish is a pleasure to use, been using it for about half a decade.
- thibran 3y agoNushell > Fish > ZSH > Bash I tried a lot of shells and that's what I ended up with.
- Hrun0 3y agoI was hesitant to switch to fish shell, but after seeing so many recommendations on HN, I gave it a shot. Been using it for a while now, and it's mostly good. The one hiccup is the syntax; it's different from ZSH, so you have to update your existing config. ChatGPT has been pretty useful for that, though.
- iLoveOncall 3y agoAt least now && works. It used to not be the case and required you to type ";and" which was incredibly annoying as you had to modify basically every single command that you found online or that people sent you. Now that && works, I don't have any big conplaints about it anymore.
- mcpackieh 3y agoFish is pretty good, but I wish it would come with fzf-like capabilities built into it by default, for automatically searching history/files/etc. Yes I know I can just install fzf and the fzf/fish integrations, I've done so. But my understanding is that the whole point of fish is that it comes well configured by default. fzf is a quantum leap forward for shell UX, this sort of functionality should be built in by default.
- zvmaz 3y agoI may be mistaken, but since I have to work with different machines that all have bash as a shell, I try not to mess with my muscle memory and stick to bash even on my own machine. But maybe I should try Fish.
- error9348 3y agoBeen using it for years. Accidentally found out a few months ago, shift+tab allows you to search for completions.
- _thisdot 3y agoI was using fish on Ubuntu in college. First job gave me a macbook and I set it up using fish. We only had one devops guy and he shared the app set up docs and all the scripts were available only in zsh or bash. I was okay with switching to zsh tbh. But the dude stopped me and then spent half a day learning and then updating all the docs with fish scripts as well! Bless him!
- kattagarian 3y agoI don't know much about shells. Fish was the first one that made everything so easy and the only downside was not being posix compliant, but i can easily call bash and run the command. I tried leaving fish and the others requires so many configurations, but fish does by default. It suits me.
- mattgreenrocks 3y agoBest part of fish is how little config is needed. I’m 41, married with kids. Old AF by some standards. I have zero patience with wasting my time configuring tooling. zsh felt like it fought me every step of trying to configure it to be halfway decent. And a lot of zsh scripts out there aren’t exactly bulletproof. It shouldn’t matter, except for the fact that if you use the shell with any regularity you will inevitably bump into edge cases that weren’t handled well by a mishmash of user scripts whose provenance is mostly copy/paste with little understanding of why it is all needed. Here’s my fish dotfiles: https://github.com/mattgreen/dotfiles/tree/master/fish https://github.com/mattgreen/dotfiles/tree/master/fish It has a submodule based plugin system (loader in conf.d), an async git prompt, my aliases, and a few env vars set. It needs no maintenance because fish provides almost everything already. The only thing I want from fish at this point is to make async prompts first-class. They are best handled by the shell, not user code, due to the state tracking.
- ansdomizzz662 3y agoAgree with everything you said. If I didn't have to write /bin/sh compatible scripts for work, I would switch to Fish for similar reasons. From a UX point of view it's indisputably ahead of every other shell and it isn't even close, to the point I'm surprised it hasn't been adopted as the default by an OS like Mac yet. I can walk my family members through terminal things with Fish and nobody gets frustrated or quits. I can't say that about other shells.
- paradox460 3y agoYou can just put a bash shebang at the top of the script and use it just fine under fish
- nonethewiser 3y agoYour fish dotfioes are a lot more extensive than my extremely small .zshrc file. What have you configured it to do?
- xwowsersx 3y agoIf I already have zsh set up to my liking, what improvements/changes, if any, would I experience if I switched to fish?
- BeetleB 3y agoNot to hijack, but also consider xonsh[1]. It's Python based, and all your scripts can be Python (or hybrid-Python). I've been using it for both Windows and Linux for over 5 years. [1] https://xon.sh/ https://xon.sh/
- ansdomizzz662 3y agoI'm interested especially for Windows, does it have any of the footguns relating to awful corporate network drive setups, $HOME, expensive prompts, and the like? I need a good shell for when I'm forced to work on Windows machines (and when WSL isn't available). Git Bash (and even plain MSYS2 bash) performance is so unbelievably awful every single time, and the fixes can be hard to determine and a giant pain in the ass, and sometimes impossible if they are due to windows defender or whatever antivirus junk the corporate environment has installed. However, Python runs fine, so maybe Xonsh would run fine? I realize I should probably just use PowerShell but I strongly dislike the syntax and would have to write function wrappers for basically every command I setup. I'm sure most here can relate to that.
- BeetleB 3y ago> does it have any of the footguns relating to awful corporate network drive setups, $HOME, expensive prompts, and the like? Not sure what you mean - can you give an example? There will be a $HOME environment variable. I never use WSL, Git Bash or Cygwin stuff. Just the normal command prompt with xonsh running on top of it. So I can't speak to performance issues. If you could give examples, I may be able to address them. Definitely should not have issues due to antivirus. It will be a program running continuously. > I realize I should probably just use PowerShell Powershell is probably the best, but I didn't want to expend energy learning it. With xonsh I can have the same config in Linux and Windows, and Python is always a plus.
- mezobeli 3y agoI think it's not Bash compatible, had issues in the past to run some programs and scripts
- justinmayer 3y agoIf you use Fish shell and Python, my project VirtualFish can make managing virtual environments a lot easier and more fun: https://github.com/justinmayer/virtualfish https://github.com/justinmayer/virtualfish
- xwowsersx 3y agoThanks for mentioning. I think it would help a bit if you copy-paste a short terminal session to show what VF looks like in operation. I know there are extensive docs, but a quick tldr/screenshot helps quite a bit in a README I find
- ireallywantthat 3y agoAm i the only one who feels fish is not worth it despite of hype? Don't get me wrong. I think that fish is really good shell. BUT... After adding the following plugins to zsh(before you chime in, it's just adding these lines,not anything configuring much. also it auto bootstraps on new install), I found out that fish is no where as good as configured zsh. 1) https://github.com/zdharma-continuum/zinit https://github.com/zdharma-continuum/zinit (plugin manager) 2) https://github.com/zdharma-continuum/fast-syntax-highlighting https://github.com/zdharma-continuum/fast-syntax-highlightin... 3) https://github.com/zdharma-continuum/history-search-multi-word https://github.com/zdharma-continuum/history-search-multi-wo... 4) https://github.com/zsh-users/zsh-autosuggestions https://github.com/zsh-users/zsh-autosuggestions 5) https://github.com/zsh-users/zsh-completions https://github.com/zsh-users/zsh-completions 6) https://github.com/Aloxaf/fzf-tab https://github.com/Aloxaf/fzf-tab 7) any good shell prompt generator like https://github.com/romkatv/powerlevel10k https://github.com/romkatv/powerlevel10k For example, I use fzf integration for tab completion. Fish's fzf integration is nowhere as good as that of zsh's. Also, posix compat and almost bash compat of zsh is plus. I acknowledge that zsh isn't perfect shell either and I have tried and failed few times in past to switch to fish. If you provide me compelling reason/s to switch to fish, I am all ears.
- AnthonBerg 3y agoSincerely: What hype? heheh –I see fish as a mostly obscure shell with some design principles. It works for me. It’s a great tool. I tried zsh; zsh was a lot slower as I set it up. Maybe I did it wrong. I think the case is that with either of fish or zsh you can’t lose. Both are great.
- em-bee 3y agowell, one of the big benefits is that i don't have to set up all this in order to get the functionality, because fish provides it out of the box.
- dang 3y agoAs it has been a while—related threads. Others? What's Happening with Fish Releases? - https://news.ycombinator.com/item?id=36875727 https://news.ycombinator.com/item?id=36875727 - July 2023 (1 comment) My shell setup with Fish and Tmux (2021) - https://news.ycombinator.com/item?id=35672358 https://news.ycombinator.com/item?id=35672358 - April 2023 (80 comments) Ask HN: Are alternative (oil, nu, etc.) shells usable as daily drivers? - https://news.ycombinator.com/item?id=34722208 https://news.ycombinator.com/item?id=34722208 - Feb 2023 (141 comments) Rewrite it in Rust - https://news.ycombinator.com/item?id=34588340 https://news.ycombinator.com/item?id=34588340 - Jan 2023 (464 comments) Fish 3.6.0 - https://news.ycombinator.com/item?id=34298157 https://news.ycombinator.com/item?id=34298157 - Jan 2023 (23 comments) Fish Shell 3.5.0 - https://news.ycombinator.com/item?id=31768405 https://news.ycombinator.com/item?id=31768405 - June 2022 (71 comments) Fish 3.4.0 - https://news.ycombinator.com/item?id=30734072 https://news.ycombinator.com/item?id=30734072 - March 2022 (90 comments) Fish 3.4.0 Released - https://news.ycombinator.com/item?id=30660587 https://news.ycombinator.com/item?id=30660587 - March 2022 (21 comments) Ask HN: Oil or Fish Shell? - https://news.ycombinator.com/item?id=30154652 https://news.ycombinator.com/item?id=30154652 - Jan 2022 (2 comments) The fish shell is amazing - https://news.ycombinator.com/item?id=29341390 https://news.ycombinator.com/item?id=29341390 - Nov 2021 (290 comments) Nsh: A fish/bash-like Posix shell in Rust - https://news.ycombinator.com/item?id=28967257 https://news.ycombinator.com/item?id=28967257 - Oct 2021 (50 comments) Fish Shell 3.3 - https://news.ycombinator.com/item?id=27663637 https://news.ycombinator.com/item?id=27663637 - June 2021 (1 comment) Fish shell - https://news.ycombinator.com/item?id=27180420 https://news.ycombinator.com/item?id=27180420 - May 2021 (118 comments) Fish Shell 3.2 - https://news.ycombinator.com/item?id=26302678 https://news.ycombinator.com/item?id=26302678 - March 2021 (128 comments) Fish is not operational on a VT220 terminal (2015) - https://news.ycombinator.com/item?id=25526237 https://news.ycombinator.com/item?id=25526237 - Dec 2020 (113 comments) New Features in the Fish Shell - https://news.ycombinator.com/item?id=24631138 https://news.ycombinator.com/item?id=24631138 - Sept 2020 (138 comments) Dolphins learn from their peers to use empty shells to catch fish - https://news.ycombinator.com/item?id=23660910 https://news.ycombinator.com/item?id=23660910 - June 2020 (8 comments) Fish Shell 3.1.0 - https://news.ycombinator.com/item?id=22314671 https://news.ycombinator.com/item?id=22314671 - Feb 2020 (1 comment) Fish: A command line shell for the 90s - https://news.ycombinator.com/item?id=21361696 https://news.ycombinator.com/item?id=21361696 - Oct 2019 (83 comments) Show HN: Fisher 3.0 – the package manager for the fish-shell - https://news.ycombinator.com/item?id=18920972 https://news.ycombinator.com/item?id=18920972 - Jan 2019 (1 comment) Fish shell 3.0 - https://news.ycombinator.com/item?id=18776765 https://news.ycombinator.com/item?id=18776765 - Dec 2018 (220 comments) Fish: A user-friendly command line shell for macOS, Linux, etc - https://news.ycombinator.com/item?id=15910897 https://news.ycombinator.com/item?id=15910897 - Dec 2017 (204 comments) Fish (Shell) for a Week - https://news.ycombinator.com/item?id=14422672 https://news.ycombinator.com/item?id=14422672 - May 2017 (2 comments) Why I'm Hooked on Fish Shell (and How to Set It Up Right) - https://news.ycombinator.com/item?id=14417046 https://news.ycombinator.com/item?id=14417046 - May 2017 (1 comment) The fish shell is awesome - https://news.ycombinator.com/item?id=14179081 https://news.ycombinator.com/item?id=14179081 - April 2017 (7 comments) Fish Shell Design Principles - https://news.ycombinator.com/item?id=11102941 https://news.ycombinator.com/item?id=11102941 - Feb 2016 (71 comments) Fish shell 2.2 - https://news.ycombinator.com/item?id=9873090 https://news.ycombinator.com/item?id=9873090 - July 2015 (70 comments) Fish shell - https://news.ycombinator.com/item?id=9566441 https://news.ycombinator.com/item?id=9566441 - May 2015 (182 comments) FISH Shell: A dynamic shell - https://news.ycombinator.com/item?id=8783150 https://news.ycombinator.com/item?id=8783150 - Dec 2014 (3 comments) Fish shell 2.1 - https://news.ycombinator.com/item?id=6626635 https://news.ycombinator.com/item?id=6626635 - Oct 2013 (151 comments) fish shell - https://news.ycombinator.com/item?id=6224524 https://news.ycombinator.com/item?id=6224524 - Aug 2013 (75 comments) Fish shell 2.0 - https://news.ycombinator.com/item?id=5723235 https://news.ycombinator.com/item?id=5723235 - May 2013 (175 comments) Fish 2.0 shell beta - https://news.ycombinator.com/item?id=5567639 https://news.ycombinator.com/item?id=5567639 - April 2013 (56 comments) Fish: Finally, a command line shell for the 90s - https://news.ycombinator.com/item?id=4073162 https://news.ycombinator.com/item?id=4073162 - June 2012 (146 comments) Fish sucks (but your shell sucks more) - https://news.ycombinator.com/item?id=2031110 https://news.ycombinator.com/item?id=2031110 - Dec 2010 (60 comments) Fish - The friendly interactive shell - https://news.ycombinator.com/item?id=820677 https://news.ycombinator.com/item?id=820677 - Sept 2009 (16 comments) Fish Shell: A User-Friendly Shell or Like a Heavily Customized zsh - https://news.ycombinator.com/item?id=811113 https://news.ycombinator.com/item?id=811113 - Sept 2009 (8 comments)
- ilyash 3y agoHi. I'm Ilya Sher, author of Next Generation Shell. That's the only shell that I'm aware of that plans to do something "radical" about the UI/UX. By radical I mean something out of the telegraph style communication paradigm. https://ilya-sher.org/2022/12/31/telegraph-and-the-unix-shell/ https://ilya-sher.org/2022/12/31/telegraph-and-the-unix-shel... https://blog.ngs-lang.org/2023/06/08/the-shell-vs-the-web/ https://blog.ngs-lang.org/2023/06/08/the-shell-vs-the-web/
- keepamovin 3y agoI like fish. It's good to have on my machine. I can see myself using sometimes. I'm used to bash. Bash for scripting definitely. I'm not sure what makes me look more like a "hacker" using bash, or using fish? I don't really care, but...ha! Just wondering. I guess fish is like, you feel like you're living in the future, but also like "this is a past that should have already been available" then you find out it has been available, for 18 years, and you wonder, "Was it me that was living in the past?" It's the kind of thing I'm scared to get burnt on, when it fails, because I already like it. I don't want it to disappoint me, because I just feel like: "new fangled, it's always gonna break." But then, it has been around for 18 years...so...hmm. So, I don't know. It looks pretty! I like to use it. But bash is, feels, more stable. Worth exploring! I'm not gonna config-it, as much as possible, but for interactive shell? I think it's good! :)