Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Fish Shell 3.2

github.com

Post reply on HN
Print view View original

101–110 of 133 posts

Re: Fish Shell 3.2

#101

Post by synthc »

I love fish, and have been using it as my shell for over 10 years, it's pretty much the first thing I install on a new system.

I usually heavily tweak the settings of the applications I use, make my own custom themes etc, but the defaults of fish are so good that I hardly changed anything.

I only installed 3 plugins (z,fzf,and virtualfish) and that's it, it's super productive.

Completion from history, persistently setting enviroment variables, defining functions, the syntax, everything is much more ergonomic and sane than in bash.

I'm sure you can tweak zsh or even bash to achieve something similar, but why bother?

Also, i don't mind the incompatibility with bash: the fish language is much more sane, and you can easily use bash if needed.

Re: Fish Shell 3.2

#102

Post by jonfw »

mhink wrote: post #91
jonfw wrote: post #79

Earlier quoted context omitted.

The parsing and setting of environment variables was always my #1 hassle with fish. I feel like I see a lot of BASH snippets that get copy pasted around that I always had to re-write or throw in a sub shell. Particularly annoying when you're trying to do something while screen sharing and somebody gives you a snippet which you have to re-write before using it- "Oh yeah it's a hassle but I've got sweet auto-complete"…

IMO, copy-and-pasting bash commands is an organizational smell to begin with, but I don't think this particular use case is a reason not to use one shell over another. If you do have a snippet of bash to run, it's easy enough to toss it in a file (with a shebang) and run it as a shell script. And as a bonus, it's reusable and you can add comments/notes for when you have to run it again.

> IMO, copy-and-pasting bash commands is an organizational smell to begin with

The people who develop the automation have to start somewhere :). If you're standing up a test environment or a PoC, writing down commands get's you 80% of the way to reproducing your results

Re: Fish Shell 3.2

#103

Post by theshrike79 »

synthc wrote: post #101

I love fish, and have been using it as my shell for over 10 years, it's pretty much the first thing I install on a new system. I usually heavily tweak the settings of the applications I use, make my own custom themes etc, but the defaults of fish are so good that I hardly changed anything. I only installed 3 plugins (z,fzf,and virtualfish) and that's it, it's super productive. Completion from history, persistently se…

This is the exact reason I use Fish. The only thing I _need_ to get installed on random servers is Fish itself.

No need to install and configure oh-my-$shell or other huge monstrosities. Most of my stuff comes from a simple homeshick[1] sync with a few files in it.

[1] https://github.com/andsens/homeshick

Re: Fish Shell 3.2

#104

Post by geoelectric »

I used fish shell for a lot of years.

Ultimately, I got tired of having to translate snippets for my use and went back to zsh for the bash compatibility. Zsh becoming the Mac default also gave me an incentive, because I prefer to use system native if it's anywhere near up to date.

But a lot of what I have to cobble together in zsh via antigen and omz was batteries-included or fisherman-easy in fish. It's very powerful right out of the box. I miss it all the time, and it may get me back before it's done.

Re: Fish Shell 3.2

#105

Post by stunt »

My favorite Fish plugins:

- jorgebucaran/fisher - Plugin manager

- IlanCosman/tide - Nice prompt with git status

- jorgebucaran/humantime.fish - Turn milliseconds into a human-readable string in Fish.

- franciscolourenco/done - Automatically receive notifications when long processes finish.

- laughedelic/pisces - Helps you to work with paired symbols like () and '' in the command line.

- jethrokuan/fzf - To integrate fzf (junegunn/fzf)

Re: Fish Shell 3.2

#106

Post by triztian »

geoelectric wrote: post #104

I used fish shell for a lot of years. Ultimately, I got tired of having to translate snippets for my use and went back to zsh for the bash compatibility. Zsh becoming the Mac default also gave me an incentive, because I prefer to use system native if it's anywhere near up to date. But a lot of what I have to cobble together in zsh via antigen and omz was batteries-included or fisherman-easy in fish. It's very powerfu…

Same here, used it for about a year but ultimately had to switch to bash/zsh variants because of compat. Servers were always bash and I always had to translate my fish scripts to zsh/bash shell when collaborating with colleagues.

I wish it'd be more popular and preinstalled on servers and macOS.

Re: Fish Shell 3.2

#107

Post by fctorial »

enriquto wrote: post #31

I'd like to use fish regularly, but I feel really attacked by the over-the-top usage of color and unrequested auto-completion. Even a "monochrome" theme I tried was shoveling many different shades of gray into my terminal. It does not seem to honor the NO_COLOR variable either. Is there any way to obtain a default configuration with everything disabled?

Why would you want to disable colors.

Re: Fish Shell 3.2

#108

Post by oblio »

rgoulter wrote: post #55
Siecje wrote: post #15

Earlier quoted context omitted.

set -e is not great and is not recommended. http://mywiki.wooledge.org/BashFAQ/105

I read this as "bash has unintuitive footguns" rather than "set -e has unintuitive footguns with its usage".

Bash doesn't have unintuitive footguns, bash > a unintuitive footgun :-)

Re: Fish Shell 3.2

#109

Post by TimWolla »

enriquto wrote: post #53
e_proxus wrote: post #35

Earlier quoted context omitted.

It's a good point, but how many of the features are useful without any colors at all? At least the auto-completion would just look like any typed text. Perhaps fish is not for you?

> Perhaps fish is not for you? It nearly is! I love fish powerful completion, just find it annoying that it is triggered automatically. Also fish syntax seems saner than bourne's, and I love it (but miss process substitution from time to time). Unfortunately, I cannot stand the flashiness. With some work, I have managed to disable all colors by setting a lot of fish_color variables in my configuration file. But the a…

You can use `psub` for process substitution, e.g. to compare two sorted files:

    diff -u (sort a |psub) (sort b |psub)
Post reply on HN