Moving to zsh (2019) • Hacker News Board

Re: Moving to zsh (2019)

#21

Post by tux2bsd » Sat, Jul 23, 2022, 5:01 AM UTC

mattpallissard wrote: post #3

I'm a zsh user, but one thing I miss from bash is /dev/tcp redirection. ~ echo /dev/tcp/google.com/80 ~ echo $? 0 ~ echo /dev/tcp/localhost/80 bash: connect: Network is unreachable bash: /dev/tcp/localhost/80: Network is unreachable ~ echo $? 1

Thanks. I've not seen that before, that's cool.

Re: Moving to zsh (2019)

#22

Post by neilparikh » Sat, Jul 23, 2022, 5:48 AM UTC

allurbase wrote: post #8

Why is zsh forced on users anyway? Are there known issues with bash? I’m sure there are - anyone have a link?

I believe it was because Bash 4 switched to GPL3, which Apple did not want to follow. See https://www.theverge.com/2019/6/4/18651872/apple-macos-catal...

Re: Moving to zsh (2019)

#23

Post by hericium » Sat, Jul 23, 2022, 5:57 AM UTC

allurbase wrote: post #8

Why is zsh forced on users anyway? Are there known issues with bash? I’m sure there are - anyone have a link?

> Why is zsh forced on users anyway? Are there known issues with bash?

ZSH isn't GPL which may be important in the smaller non-Linux part of UNIX-like world. I would very much like to see ZSH in FreeBSD's base system already.

BTW, forced how?

Re: Moving to zsh (2019)

#24

Post by homulilly » Sat, Jul 23, 2022, 7:26 AM UTC

LeoPanthera wrote: post #5

I've been using bash since the early 90s and I'm now in my 40s so I think at this point I just have to accept that I will never use another shell. On Macs, the current version of bash can be installed from Homebrew and you can set it as your default shell in the SysPrefs, in Users > Right-click you > Advanced

This still presents an issue with shebang lines, though. I use ‘#!/usr/bin/env bash’ to work around this but occasionally have to modify other peoples scripts if they’re relying on newer bash features.

Re: Moving to zsh (2019)

#25

Post by cyberpunk » Sat, Jul 23, 2022, 7:28 AM UTC

hericium wrote: post #23

allurbase wrote: post #8

Why is zsh forced on users anyway? Are there known issues with bash? I’m sure there are - anyone have a link?

> Why is zsh forced on users anyway? Are there known issues with bash? ZSH isn't GPL which may be important in the smaller non-Linux part of UNIX-like world. I would very much like to see ZSH in FreeBSD's base system already. BTW, forced how?

There was a MacOS update that set everyone’s shell to zsh instead of the default (ancient) bash.

Hardly insurmountable, but the change was a “forced” part of the upgrade.

Re: Moving to zsh (2019)

#26

Post by sph » Sat, Jul 23, 2022, 7:41 AM UTC

runjake wrote: post #12

mattpallissard wrote: post #3

I'm a zsh user, but one thing I miss from bash is /dev/tcp redirection. ~ echo /dev/tcp/google.com/80 ~ echo $? 0 ~ echo /dev/tcp/localhost/80 bash: connect: Network is unreachable bash: /dev/tcp/localhost/80: Network is unreachable ~ echo $? 1

Why? There’s nc.

I tend to prefer telnet to test connections because its output is more verbose.

We need a friendlier netcat, with better output. Call it netdog.

Re: Moving to zsh (2019)

#27

Post by remuskaos » Sat, Jul 23, 2022, 7:44 AM UTC

I've switched from bash to zsh a few weeks ago and overall, I'm pretty happy. Menu based auto completion for example is extremely nice.

But I could never get auto complete for rsync to work. I have some hosts in ~/.ssh/config (think "Hostname prod01" etc) , and in bash auto complete works for ssh, scp and rsnyc ("rsync prod01:someFile .")

In zsh, this only works for scp and ssh, but not rsync, and I haven't found a way to make this work.

Does anyone know how to get it to work like in bash?

Re: Moving to zsh (2019)

#28

Post by noisy_boy » Sat, Jul 23, 2022, 8:12 AM UTC

thebitstick wrote: post #6

First thing I do for any *nix install is immediately install Fish. Like many younger computer users I prefer rainbow barf.

I tried fish and really liked it until I tried to run one of my numerous helper scripts and was faced with syntax error; too lazy to update so many scripts.

Re: Moving to zsh (2019)

#29

Post by hericium » Sat, Jul 23, 2022, 8:18 AM UTC

cyberpunk wrote: post #25

hericium wrote: post #23

Earlier quoted context omitted.

> Why is zsh forced on users anyway? Are there known issues with bash? ZSH isn't GPL which may be important in the smaller non-Linux part of UNIX-like world. I would very much like to see ZSH in FreeBSD's base system already. BTW, forced how?

There was a MacOS update that set everyone’s shell to zsh instead of the default (ancient) bash. Hardly insurmountable, but the change was a “forced” part of the upgrade.

Changing users' default shell is not the same as forcing it on users. You can chpass(1) and set a different shell.

I'm not too comfortable playing devil's advocate here as Apple really does force shitty changes on users. But this isn't one of those cases.

Re: Moving to zsh (2019)

#30

Post by ccouzens » Sat, Jul 23, 2022, 8:41 AM UTC

tambourine_man wrote: post #11

mattpallissard wrote: post #3

I'm a zsh user, but one thing I miss from bash is /dev/tcp redirection. ~ echo /dev/tcp/google.com/80 ~ echo $? 0 ~ echo /dev/tcp/localhost/80 bash: connect: Network is unreachable bash: /dev/tcp/localhost/80: Network is unreachable ~ echo $? 1

I think that’s Linux-only, right?

It's in the /dev/ folder so it looks like a device file provided by the operating system.

But it's not. It's a bash built in pseudo file. So it should work in bash on other operating systems.