FISH (Friendly Interactive Shell) by Bash Boomer

[@LukeSmithxyz]

URGENT! Read this: lukesmith.xyz/deletion

[@Magnus_E]

holy canoly man hahaah thanks for telling, returned to ur channel after a loooong time :D stay strong and healthy !

[@YandryPozo]

not found error on that link

[@YandryPozo]

@Max შემიწყალე you are the kind of person that reads an email with subject Urgent

[@YandryPozo]

@Max შემიწყალე you have bought so many gift cards from Target

[@nirgunawish]

10:50 bruh same i never expected you to do that

[@alexxmde]

Family tell you to go fishing because you never leave your shell... And that's how you react

[@kofteistkofte]

I'm using FISH for 2 years and I'm really happy with it. At the start it was bit strange to change the things I do but at the end, I'm perfectly happy with it. Also, you can chage your default shell with "chsh -s /usr/bin/fish"

[@raresdobre2497]

Nvim and fish? What are you, a zoomer?

[@raresdobre2497]

@@MoonNuggetFilms /g/ redpilled me about it. The speed difference between it and vim is huge. I'd use kakoune but Ctrl-space is too comfy

[@himselfe]

@@MoonNuggetFilms: there is a third option.. might be in bed with a sexbot.

[@douwehuysmans5959]

Vim with Emacs bindings, Very Nice

[@PabloAndresDealbera]

@@jdegreef says you. I'm on the bed with Arch GNU/Linux. Did I tell you I use Arch?

[@jan_harald]

@@jdegreef ahem, there are linux 4 android apps (without root too), and you can ssh...so not a real excuse ;p

[@sethcenterbar]

zsh user here. I had no idea about the - for arguments, that is phenomenal.

[@daleryanaldover6545]

4 years later, same zsh user here. I am shocked 😮

[@Cobalt985]

I literally only use it for colours and autocomplete

[@riley3269]

zsh syntax highlighting and autocomplete can be set in a few seconds. Plus it is POSIX compliant.

[@riley3269]

@@jamesbissick3439 Why?

[@Mustafa-gd2rp]

​@@7yep4336dfgvvh So you would switch to fish, run cd with autocomplete, then switch back to bash? 3 commands to run 1, that means 3 times the effort and time, things that all of these shells are trying to optimize

[@nykal1510]

@Mohamed Haddi Why do you write fish scripts? I have /usr/bin/sh linked to dash so scripts use it, but use bash as my default shell. That way scripts run efficiently - dash is unusable in a terminal but it's fast

[@porky1118]

You forgot the most important feature: If a program outputs something, which doesn't end with a newline, fish automatically adds a newline, and indicates, that it was put by fish.

[@MaazAhmed]

2019: "I might end up using Fish anyway" ( 11:34 ) 2021: "The fish shell is not a shell and is cringe to use" (kzbin.info/www/bejne/bnK0oJWmpt6Gd7c)

[@francescovolpini]

i think people know what he thinks about it now?

[@desktorp]

WANTED: pcfish (POSIX-Compliant Friendly Interactive Shell)

[@Newbyte]

May I know why?

[@giuseppelamalfa2966]

@@Newbyte interoperativity is cool

[@riley3269]

Zsh

[@cmplstofB]

I think ble.sh on Bash is a nice project.

[@singha360]

There's Fizsh

[@yamahaespen]

For people that have limited experience with Linux like myself fish made me like using the terminal a lot more. It's just way more interactive and nicer to look at as soon as you improve the color palette. Some of the default colors are too sharp, especially the red and the dark blue

[@valbogda5512]

I love fish :) I've been using it for 3 or 4 years now and can't imagine anything else supplanting it for me. People should check out the design principles of fish and then try it for themselves. They really deliver.

[@samuelwaller4924]

One of them is literally "Configurability is the root of all evil" lmao you're kidding, right

[@valbogda5512]

@@samuelwaller4924 It's not that extreme. FISH is perfectly configurable.

[@Noname-67]

​@@samuelwaller4924 source?

[@valbogda5512]

@@samuelwaller4924 It's not that extreme. Fish is perfectly configurable.

[@edvonrattlehead2135]

And this video will now get a crapton of views

[@bool2max]

Nice, a fish video. I switched to it a couple of weeks ago and seriously the best thing is that variables with spaces inside them, e.g. set -l name "Some Name" expand to only 1 argument in the shell: e.g. rm $name would actually expand to rm "Some Name" can't look back at traditional shells since

[@bool2max]

​@@bashisobsolete.pythonismyn6321 Yeah a lot of stuff is more readable ootb, for example you can redirect stderr with a carret (^), but for some reason they deprecated that in the latest release.

[@johnandaway]

Just so that people know, POSIX sh supports this as well, using a “special” syntax: rm "$name"

[@supersonictumbleweed]

Thanks for letting me know why I'd hate fish before I even install it. This would make most of my scripts unusable

[@bool2max]

@@supersonictumbleweed It wouldn't. Putting variables inside of doublequotes still expands the variable normally, just like in bash.

[@supersonictumbleweed]

@@bool2max so it's inverted, great

[@YTNoobProductions]

I use fish myself, both at home and at work. I suggest writing scripts in bash or sh and using fish only as an interactive shell. I have the my users shell set to fish in /etc/passwd and as long as your scripts have the bash or sh shebang (#!/bin/bash or #!/bin/sh) as the first line in them you will be fine, because then they will be interpreted by those anyway. When I was using zsh I even tried it out in larbs and everything (except for the .bashrc stuff of course) seemed to be working properly. Fish is really convenient if you use the command line a lot, but personally I want my scripts to be POSIX compliant, because they work on more systems that way and I need them to do that at work. In some distros /bin/sh points to bash, but in debian and it's derivatives /bin/sh points to dash (debian almquist shell or whatever) for example. Both of those can run POSIX compliant scripts as far as I know, so they will function the same way. TL;DR: When you want to switch your interactive shell, then make sure your scripts have the shebang in front of them and you will only need to worry about rewriting your bashrc.

[@WINTERMUTE_AI]

Love the colors, reminds me of my old Commodore 64 BBS days. :)

[@migue7490]

I'm currently using zsh and I moved to i3 from KDE, enough changes for now XD, but I'll take a look at this. Nice vid.

[@p6n7l]

now keep zsh and switch to xmonad

[@mgord9518]

Now switch to plan9

[@porky1118]

I started using fish a few weeks ago, and it didn't take long until I set fish as the default shell for all my systems and profiles

[@johnandaway]

There are two reasons why I don’t use fish: it’s slow, and it uses a syntax that isn’t familiar to me, nor POSIX compatible. While I like the ideas behind fish - a pre-configured, usable shell with powerful auto-completion - I just wish it were POSIX-compatible.

[@lordadamson]

Why is POSIX compatibility important?

[@mina86]

@@lordadamson, for me it’s important because I tend to write shell scripts which I distribute with others. If I write them in POSIX shell, I can make them work on pretty much any modern Unix-like system without that much hassle. However, having to switch syntaxes between POSIX - when writing scripts - and fish - when in interactive shell - puts too much cognitive load as is not worth having syntax highlighting on the prompt.

[@cosmojg]

At the very least, fish is faster than bash.

[@johnandaway]

Adam Zahran: It’s great because it’s portable and works everywhere, which is important for me, but of course, not for everyone (which is why some like fish and others dislike it)

[@johnandaway]

Cosmo Guerini: I don’t know, maybe - I’ve just noticed, that over SSH, fish is much less responsive than shells like dash and ksh.

[@typingcat]

"And when you couldn't find one...?" "We went fishing."

[@linuxramblingproductions8554]

Fish seems more well designed then bash it sucks a bit that bash is the standard for 90% of stuff

[@tc40390]

5:18 I was expecting you to enter: $ echo "It's botnet!"

[@alessandroceloria]

He could add an elif for chrome to print that

[@Pterry23real]

I like fish, using it since 2017. omf (oh my fish) is a good addition too. Some downsides are, that you still need to run some bash snippets in bash, but maybe the update you talked about will change this. Also, as soon as you have to ssh into some random servers you have to use bash suddenly. Even worse on docker containers, where most of the times only dash is available.

[@Lindholmer5k]

Oh sweet, im dyslectic, so im sure this will help me tremendusly... iv spent countless hours trying to find the right commands, only to find out iv spelled it wrong

[@fcolecumberri]

zsh and fish might have super sweet stuff when used on the terminal (especially after tweaking them to your taste), but my scripts still starts with #! /usr/bin/bash. My advise is: Use the correct tool for the correct problem.

[@fjonesjones2]

I've been using fish as default for 9 months... it's great for me and I love it too, with Linux Mint 20.... if I need bash... I just type bash at prompt... change back .. type fish.. ;-)

[@scarab5Q]

This is great! Love seeing you do screen screen casts when you can. Would highly advocate doing a video on tmux aswell as useful cli navigation things like fpp, fzf and fzy. But only when you can because I think it would be a real shame if you were to not do all this and resent it as it got in the way of other things you wanted to do.

[@YTNoobProductions]

I love tmux so damn much. I haven't taken the time to set up a tiling window manager on my ubuntu machine at work so I just run the terminal in full screen with tmux, with remapped keys so I could navigate between panes with vim-like keys. It can pretty much be a tiling window manager for your terminal. You can even set up powerline for tmux if you like that sort of thing.

[@timobachmann5934]

@@YTNoobProductions Agree, I am using tmux at work because it would take me too long to set up proper i3 and I know I'd spend more time ricing it than actually working but there's still a difference between tmux and a tiling window manager... Tiling window manager for a terminal, yes. But the concept of dwm based window managers is to have everything tiled which is amazing once you've got used to one. In the end you do most stuff in the terminal anyway so you get along with just tmux + browser, but there's still a big difference.

[@YTNoobProductions]

@@timobachmann5934 Yeah I know the differences. I have been using i3 at home for quite a while now. I have tried using Awesome and dwm but I had a hard time getting used to having predefined layouts instead of the tree mode or whatever you call it that i3 has.

[@alecstewart212]

Hello, avid fish-shell user here. So a couple of things: 1. Path So fish has a separate variable for a users path. Whether or not this is useful compared to sh/bash/zsh, I don't know. It's called `fish_user_paths` and you should set it with `set -x fish_user_paths /paths/you/want`. *Do not use `set -g`.* Or at least try to avoid it as much as possible. You can use it for `PATH` if you'd like, like so `set -xg PAHT $PATH /sbin` but other than that try not to use `-g` with set. 2. Login shell # === Start X at login === if status is-login if test -z "$DISPLAY" -a "$XDG_VTNR" = 1 exec startx -- -keeptty end end 3. Aliases and Abbreviations You can have both. `alias` is basically you wrapping something in `function` (well, sorta), so depending on your uses it may or may not be better to just wrap it in a function. Most of the time, for like `ls` combinations, alias is better. I would use `abbr` for like complicated package manager commands. That way you don't have to type it all out, but you see the command once you press enter so you know what you're executing. Thing to remember is `set -x VAR ARG(S)` is just POSIX shells `export VAR=ARG(S)`. But you can also use `export` now.

[@SensualSquirrel]

I love fish shell, and have advocated it's use for years.

[@symq]

The fact that fish is not POSIX compliant was, of course, a deliberate design choice, and in my humble opinion a good one. Keeping compatibility with old standards is a huge problem (not only) across all of technology. It slows progress, encourages bad intuition/habits, etc. and POSIX is no exception. The reason many of the new and theoretically superior programming languages have a hard time getting adopted and many of the old programming languages have a hard time being changed into something better is exactly backwards compatibility and industry inertia. Of course, backwards compatibilty lets us build on old foundations and newer technologies often aren't quite the answer to everything either. But still, at the risk of being a zoomer, I welcome projects like fish and don't mind them breaking compatibility.

[@symq]

jdegreef Without IPv6 the internet wouldn't work today. So should we stick to IPv4? Just as you said, we have to improve standards. Sometimes this requires breaking backwards compatibility.

[@hwfjj1989]

@@symq The IP change was a needed change because of limitation of old standard. Breaking posix compliance is not a needed change. Yes innovate more but don't break stuff needlessly. There is a difference that should be clear if not lets talk more about it.

[@hwfjj1989]

@@symq also the internet would still work we just could not add more devices to it without refactoring the globally available IP addresses. Hence why we are running both ipv4 and ipv6 during the transition between them as to not break stuff till everything gets updated.

[@bigshaqsmathematicalinstit3318]

This is my favorite boomer.

[@jetardeshna3449]

Doing god's work teaching us noobs these things. Love the content, stay strong, hope you grow inf-folds.! :wq

[@MrXardasya]

True zoomer shell

[@Microphunktv-jb3kj]

Boomer - bash? Millenial - zsh? Zoomer - fish?

[@PantsYT]

No, "zsh" stands for zoomer shell

[@MCLooyverse]

Standards are nice, but then so is being good at what you do. I understand the irritation when you're used to one way, but somebody or something does it another way, but then I also understand wanting to do something in a way that someone who isn't already used to the standard would prefer.

[@azngoku666]

wow i've used fish for years and didnt know about abbreviations?! also seconding the bobthefish recommendation

[@ionichi]

Q: How many existentialists does it take to screw in a light bulb? A: Fish.

[@hotscriptgg]

Luke, you should also check xonsh it is cool as well

[@thomassasuke2101]

When you explained abbreviations in fish I immediately thought of global aliases in zsh. They are pretty much the same thing so maybe people want to check that out.

[@austingarrigus755]

Fish is interesting but not exactly usable in my opinion. I switched to it for a good couple months but gave up on it after getting tired of the frustration. Not being posix compliant is a complete deal breaker for me. The whole thing feels like it was developed with the mindset that working with standards is too hard. Especially annoying was having to do several layers of mental mode-switching any time I needed to connect to any other machine not running fish. There wasn't a common ground syntax I could fall back on to maintain sanity while swapping back and forth.

[@lordadamson]

why is posix compliance important?

[@austingarrigus755]

@@lordadamson It's important because it's *the* standard for how the system should behave. It means you can expect a reliable result when you ask it to do something. If you download a shell script, it will do exactly what is intended. Once you're used to how to interact efficiency with a POSIX system, you understand why things are done the way they are. Any POSIX system you touch will have a common set of instructions. Like I said previously, if you need to switch between a system running fish and other machines you eliminate any potential ease of use gained from fish.

[@alexzander__6334]

3:12, respect for using arch

[@BrunoAraujo677]

Is good to have a affirmation from a experience user in what is annoying in fish, I completely agree

[@jerrygreenest]

Not POSIX-compliant? Uh oh, I so wanted to try it, but...

[@jasonk4442]

Your a beast on a computer bro. You earned yourself an active subscriber and I look forward to your future videos. Keep up the amazing work.

[@CoWinkKeyDinkInc]

you're*

[@amalldekan1432]

@@CoWinkKeyDinkInc shut the fuck up, he communicated the idea that's all that matters

[@Yaxqb]

I fully agree that fish is a weird shell with awesome features. Someone should fork the interpreter from the fish interface and slap a bash backend on it. It's such a shame that the shell has so strong opinions on being non-posix🤔

[@jkbenedict]

YES! Fish is the most awesomely cursed thing that I have followed FOREVER. Finally, it gets some lime light! Thank you!

[@JeroenKnoops]

I love fish! I only got one 'problem' with it.. How it handles removing a symlink. In bash you remove a symlink with `rm `, but in fish you will remove the original directory when you do that, you will need to use `unlink `... I think the bash version is wrong, but people are used to it.

[@amerikraine3401]

You can just change your default shell such as: chsh/usr/bin/fish instead of typing fish in the bash shell

[@MaazAhmed]

Yeah, and you can list available shells by using 'chsh -l' and use 'chsh -s shellLocation' to change it.

[@bendover4728]

Fish feels like... Holy Carp!

[@azechele]

If you didn't know about them, I greatly suggest you to try and use a REPL shell. I personally use eshell (since I live inside emacs, even my wm is emacs so...), but there are others, and I personally never looked back beside the very few ncurses programs I use.

[@bruderdasisteinschwerermangel]

I guess fish for "standard use" and doing the usual stuff, and bash for the scripts although having two shells kinda defeats the purpose of switching to another one why is fish not POSIX compliant? Did the devs give a specific reason?

[@LukeSmithxyz]

"Hey dude that's not modern, man. Haha that syntax is obsolete, bro!"

[@LukeSmithxyz]

I say this, but if you check their Github issues on this there's a lot to that effect.

[@bruderdasisteinschwerermangel]

@@LukeSmithxyz backwards compatibility is obsolete? Lmao okay then

[@alessandroceloria]

@@bruderdasisteinschwerermangel Backwards cpatibilty can get obsolete when it's too much (just look at Microsoft struggling with Win10 because they have to keep compatibility with f-ing 95), but yeah completely cutting off POSIX compliance is totally crazy (and stupid) too.

[@bruderdasisteinschwerermangel]

@@alessandroceloria it makes sense to scratch backwards compatibility with things that are obsolete by definition. But POSIX is just so heavily used, I don't see the point behind it, except "being different"

[@Headcrabman9999]

>abbreviations in bash That sounds absolutely fantastic

[@TheCerule]

I use Zsh with plugins that mimic some key Fish features like "zsh-users/zsh-autosuggestions", "zsh-users/zsh-syntax-highlighting", "zsh-users/zsh-history-substring-search". this way I don't need to deal with the non-posix-compatibility.

[@nindzafa]

Fish Shell is excellent software. You should try fisherman (Fisher) to manage your shell plugins. It supports Oh My Fish. And you've got to try bobthefish (a Powerline-style, Git-aware fish theme). That's all you have to do now.. xD

[@nindzafa]

I expect a new vid tommorow with you going through fisherman and bobthefish.

[@xthebumpx]

Fisher is a great manager, at least IMO. One of the reasons I use Fish instead of Zsh.

[@00chilli00]

I was about to comment , then I thought - someone must have already made the suggestion. +1 for bobthefish !

[@paulriddle2254]

I have been using fish for more than 4 years. Never bothered to learn much about it really, was just doing super basic stuff.

[@framegrace1]

No POSIX, no shell. It's a no brainer, no matter how nice it is.

[@haystackdmilith]

Lack of compatibility with Sh/ Zsh functions is main reason why I will never use it.

[@WinterWeaver]

I like your pastel colour scheme... Do you have your dotfiles or config files hosted on github? Or maybe a name for the colour schemes?

[@ivanovyordan]

Setting fish as a default shell is pretty easy actually. First, you have to add it to your shells list: sudo echo $(which fish) >> /etc/shells And then change your shell: chsh -s $(which fish)

[@hwfjj1989]

It is not that simple because of the posix noncompliance

[@hwfjj1989]

as in yes you can change it like that but break a lot of things in the process till you switch back and do what Luke is doing.

[@Pumpkin-Link]

BTW if you guys use SSH a lot, install MOSH (mobile-shell) right now. it has predictability character printing, so it basically has no connection input lag at all, on top of that it also runs over encrypted UDP to make it faster and can re-connect automatically if you change IP or something. You can install it in your phone with Termux and connect to a server with a 2G connection inside a moving bus and it still keeps working. I've been using it to connect to my Google Cloud VM and it works like heaven, way better than using the official GC app embedded terminal

[@stupidYoutube]

What was that package I downloaded? I'm pretty sure it started with an "f" > pacman -S f Then it'll show (in grey) the last one you typed. Let's say it was "firefox" Then you think... no... that wasn't it... Then you press "up" And now it says pacman -S feh Ah, that was it! Being able to traverse history from a start point is fucking awesome. We also have fish_config which spins up a local webserver to deal with config in a graphical way. Pretty cool, especially for new folks. I swim in my terminal. Oh, and fish also has just simply auto complete love. Let's say you have a python file lumped in with a hundred txt files that you can't remember the name of. Just type ".py" and press tab. It'll find it.

[@GAMasterMedo]

stop using arrow keys! ctrl-p is 'up'

[@stupidYoutube]

@@GAMasterMedo The problem is... K is supposed to be up! Hard to do in a shell.

[@douwehuysmans5959]

The reason for the && is that it shortcircuits, which is really useful as its an implicit if statement, same for || which is an implicit else statement

[@soumyabanerjee1995]

The command 'chsh' might be helpful to change the shell from bash to fish. Though I am not very sure.

[@MrZombieSwamp]

this video definitely aged like milk :P

[@rednight2476]

It's sort of a C shell of the current year. Lots of user convenience features, not really compatible with a normal shell. You can make another user on your system with the same UID and a different shell to play around with ti, or just use it optionally as a login shell. su - fish_user to switch to that enviroment or just login with that user.

[@GioGziro95]

Why can't they add an option for POSIX-compliance, like _fish --posix_ or something?

[@depressivepumpkin7312]

for me big irritation is the lack of HereDoc, custom shell scripting language, the dollar sign thingy, even the custom rc file name and location, and finally, AGAIN custom syntax for autocompletion

[@juliopcrj]

"I can't use it as a login shell" check out the command "chsh".

[@brainplot]

He didn't mean that. He meant that Fish has its own (different) way of setting up $PATH and other things. Having bash spawn a fish process allows to inherit that stuff from Bash.

[@motbus3]

Wouldn't it work I'd settings from profile?

[@W_0_W]

@@brainplot It is not true. Bash uses a bunch of initialization files like .bashrc, .profile, .bash_profile, and so on. Fish only uses one file: ~/.config/fish/config.fish, so it's actually the same way, even better. I personally removed all bash trash from my computer, put all settings into fish config and everything works perfect!

[@isamert1799]

Fish is just an interactive shell and nothing beyond that. For example, I also use st as my terminal and changed the default shell of st to fish which is a more elegant solution to setting fish as default. I set my PATH variable and bunch of other variables in .profile and fish inherits them. Just don't use it as your main/login shell, make it your main interactive shell. It doesn't really make sense beyond that. Even though it has better syntax than bash, writing scripts in fish is bad choice in the long run for bunch of reasons, IMO.

[@channel11121]

I deadass got a fish market training video as an ad.

[@jessedarko]

Been using fish since 2013. It's the best.

[@prometheus6474]

by the way to show what an alias actually does on interactive dash bash or zsh just do set -o xtrace

[@rechade]

Having trouble playing this video, just getting a spinning circle. Was playing previously.

[@Microphunktv-jb3kj]

Friendly Interactive Shell Hell F i s h

[@defvii]

Switched to this due to the high overhead on zsh with a framework. Fish is great out of box, other than choosing another inbuilt theme/colour set (Nord, which I use everywhere) I get all the features bash doesn't have plus some better design paradigms all in a lightweight shell. Of course, as much as bash sucks, its still very feature complete, available everywhere/POSIX compliant and I already know it. So my scripts are all bash and occasionally I have to call "bash -c" for some complicated one liners (this is rare though...)1

[@elidrissii]

The only reason I prefer zsh is POSIX compliance.

[@idtyu]

I like fish non posix compliant syntax, purely because I use php /mysql a lot, and using semicolon to run multiple commands is really nice... Function declaration is similar to sql as well. Also, at least on Fedora and centos , you can set fish as default shell

[@jdgregson]

The most compelling reasons to just stick with Bash are: 1) it's already on the production servers 2) you can't throw random programs and shells on production servers

[@jdgregson]

@Panama Jack Answer: ANY production server. In an enterprise environment, any change to the system must go through change management. So if you're a system administrator and you prefer to use Fish, too bad, you can't just install it on every server you log into. For that reason I've decided to become proficient at what's already there: Bash.

[@jdgregson]

@Panama Jack I see what you're saying. Yes, for personal use or for use in small organizations, it's a neat shell to use. My comment was simply saying that, since I've worked in large organizations with change management and likely will again, it's easier in the long run not to get used to things that I can't use everywhere.

[@killistan]

add /bin/fish (or whatever the full path is) to /etc/shells! (then you can chsh -s /bin/fish)

[@Zuschauer19]

Your video helped me a lot. Keep up the good work.

[@mina86]

Regarding the abbreviation problem, you could try ‘set -x’. That could be too noisy or confusing in its own right though.

[@tiberiusvetus9113]

zsh also supports abbreviations and auto expanding aliases.

[@deserve_it]

Nice. But i am personally have nor problems with highliteing and identation. I changed my default terminal scheme to vi instead of emacs. So when you want to type some ifs or fors , anything that requires multilining you simply press "v" and vim is opening. You should change it in your bashrc for replace the nano. Arrange it in your vim , with all highlithing and identation , close it by pushing "x" in normal vim mode. It runs immediatly in your terminal window.

[@Strazil1]

I have been using fish and oh my fish a while now and i rly love it.. its autocompletion does it for me. You can find a nice powerbar theme called bob the fish. Are you using Hyper? I didn't update yet and switched back to Terminator since Hyper doesn't work well with Vim..

[@andrewjarrett132]

hey Luke, super helpful. my only shell experience is with bash, but this video got me to start playing with fish and i'm loving it so far. would love a follow up on your experience so far, if you're still using it!

[@L9TurboBoost]

self-conscious boomers don't exi...

[@Ribula1]

1:10 amd im already impressed! :0

[@wildhomestead8498]

oh-my-zsh for life

[@rmcellig]

Thanks Luke!! Looking forward to a follow up ! 😀

[@dj-no]

Thats not luke he uses zsh!!!

[@cam2291]

Btw you can get the same completion and highlighting in zsh if you install zsh-autosuggestions and zsh-syntax-highlighting then add this shit to your zshrc: source /usr/share/zsh/plugins/zsh-syntax-highlighting/zsh-syntax-highlighting.zsh source /usr/share/zsh/plugins/zsh-autosuggestions/zsh-autosuggestions.zsh

[@jasoneastman6797]

Man, I tried using this for a week or two and I could stand it. It would just get in my way.

[@yagot2323]

fish? nvim?? firefox??? what happened to this guy :P

[@pearljamrules1]

Fish is good but it behaves differently than bash. You can get all the same features with zsh and a few add-ons and it's fully compatible with bash.

[@bobbros3414]

Uh oh...

[@patrickprucha5522]

Thanks for the info! Cheers.

[@EthanLR]

I like xonsh, because it utilizes python which is far more readable imo.

[@ashleybishton742]

Yes I love fish

[@insidetrip101]

the problem with moving to something like fish is that its just an extra thing to learn. Yeah its nice, but like you say, because its not POSIX compliant, you're still going to have to know bash/sh (assuming that you're going to use other people's code) simply because that's what the majority of the scripts are written in. I actually do like the syntax of fish (Bash's syntax really sucks compared to the majority of other programming languages), and a lot of its features are pretty nice. I know this is the sort of thing that you are lamenting in the video, but the nice thing about trying to stick with programs that are portable isn't *only* that you can port programs to obscure hardware, but also that its just easier for the user to integrate into their toolbelt. With that said, its easy to be "too portable," but fish is a decent example of exactly what I wouldn't recommend to a new user (even though it might be easier for them to learn), its going to cause them frustration when they inevitably have to use bash.

[@RandomGeometryDashStuff]

05:01 BEWARE, this is incorrect when BROWSER='2 = 2 -a firefox' to fix it use quotes: if [ "$BROWSER" = "firefox" ]

[@green4ao]

Hi Luke, which arch-distro and window manager you are using?

[@bigfootisjustreallyshy]

I finally tried fish today after using ksh for about 6 months, after hearing about it for the first time around the time this video came out. I absolutely hate it. it took a few hours to covert my custom POSIX functions and other configurations, the syntax is garbage. Not to mention the time it took to fix the builtin fish variables for the vim mode prompt so it didn't look like complete dog shit. I would rather use Z shell if i want a flashy shell.

[@Puzomor]

i use fish as my login shell, and have never had any problems with it

[@kaihendry]

functions, aliases and abbrs? bloat! :P

[@GAMasterMedo]

haha based on your preferences: it has colors? bloat

[@fleefie]

@@GAMasterMedo If it has more than 1000 lines of code it's a bloated shell.

[@illiadenysenko7776]

in fish there are no aliases :D aliases are just functions