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

Kali Linux 2020.3

kali.org

Post reply on HN
Print view View original

11–20 of 102 posts

Re: Kali Linux 2020.3

#11

Post by idoubtit »

I think the move of Kali Linux from bash to zsh is sane. I sometimes have to use the default shell of Linux distribution, especially on servers, and my main pain points with bash are:

- The history is editable by default. If I move to a previous history line and change it, the old line disappears. Hitting Ctrl-c will remove it from the history.

- If I use simultaneous shells (screen, tmux, or several ssh connections), the history saved will be the one of the last shell to quit. The bash config `histappend` should be the default, IMO.

- Most of the time, I search the history by the beginning of the command I just typed, which zsh maps to alt-p and which bash does not map by default. I rarely use the ctrl-r search.

- No way to pause a command and view the man. With zsh, `git clone` will display `man git-clone`, then return to the incomplete command line.

- No way to set a command aside. E.g. if I realise while typing that I'm not in the right directory, `git clonecd src`.

Re: Kali Linux 2020.3

#12

Post by Twisell »

richrichardsson wrote: post #10
ibotty wrote: post #6

Earlier quoted context omitted.

I am pretty sure the default shell was csh on OpenStep and thus most likely on NeXTSTEP as well.

Having watched a bunch of videos of people who bought NeXT computers recently, I can confirm that the shell they saw when running Terminal.app was csh. It would be a hell of a coincindence if all of them had happened to change from the default to csh.

Also MacOS switch to zsh was pretty recent (used to be bash). https://support.apple.com/en-us/HT208050

Must have been some confusion here.

Re: Kali Linux 2020.3

#13

Post by Neil44 »

idoubtit wrote: post #11

I think the move of Kali Linux from bash to zsh is sane. I sometimes have to use the default shell of Linux distribution, especially on servers, and my main pain points with bash are: - The history is editable by default. If I move to a previous history line and change it, the old line disappears. Hitting Ctrl-c will remove it from the history. - If I use simultaneous shells (screen, tmux, or several ssh connections)…

Pause command - I usually hit home, insert a # then enter then man then get the command back and continue. Or tmux it. Didn't realise zsh had that shortcut.

Re: Kali Linux 2020.3

#14

Post by saagarjha »

idoubtit wrote: post #11

I think the move of Kali Linux from bash to zsh is sane. I sometimes have to use the default shell of Linux distribution, especially on servers, and my main pain points with bash are: - The history is editable by default. If I move to a previous history line and change it, the old line disappears. Hitting Ctrl-c will remove it from the history. - If I use simultaneous shells (screen, tmux, or several ssh connections)…

> No way to pause a command and view the man.

^A, ^K, m, a, n, space, ^Y, enter. Upon exit, ^Y.

> No way to set a command aside.

^A, ^K. Grab it again with ^Y.

(Yes, these are all readline shortcuts. If you think they’re a bit long, bind them to something shorter in your inputrc.)

Re: Kali Linux 2020.3

#15

Post by rytis »

Neil44 wrote: post #13
idoubtit wrote: post #11

I think the move of Kali Linux from bash to zsh is sane. I sometimes have to use the default shell of Linux distribution, especially on servers, and my main pain points with bash are: - The history is editable by default. If I move to a previous history line and change it, the old line disappears. Hitting Ctrl-c will remove it from the history. - If I use simultaneous shells (screen, tmux, or several ssh connections)…

Pause command - I usually hit home, insert a # then enter then man then get the command back and continue. Or tmux it. Didn't realise zsh had that shortcut.

Instead of home+#+enter try alt-#

Re: Kali Linux 2020.3

#17

Post by saagarjha »

With a heavy heart I join the rest of the zsh discussion because these aren’t even factual:

> You can do a lot of advanced things with bash, and customize it to do even more, but ZSH allows you to do even more.

Bash can do a lot of things zsh can’t, and vice versa.

> Fish is a nice shell (probably nicer than ZSH), but realistically it was not a real consideration due to the fact that it is not POSIX compatible.

Neither is zsh, really. There’s emulation modes but I never got the impression that fidelity was a goal there.

Re: Kali Linux 2020.3

#18

Post by sgillen »

ggm wrote: post #8

Fascinating that the conversation goes to zsh over bash. You'd think a decent Bluetooth risk tool was more relevant given the covid19 dependency on more bt always on and so more bt drive-by

I mean, anyone who cared was not waiting on the tool being shipped with kali linux to start using it. So including it is mostly a convenience thing .

Re: Kali Linux 2020.3

#19

Post by dima55 »

saagarjha wrote: post #14
idoubtit wrote: post #11

I think the move of Kali Linux from bash to zsh is sane. I sometimes have to use the default shell of Linux distribution, especially on servers, and my main pain points with bash are: - The history is editable by default. If I move to a previous history line and change it, the old line disappears. Hitting Ctrl-c will remove it from the history. - If I use simultaneous shells (screen, tmux, or several ssh connections)…

> No way to pause a command and view the man. ^A, ^K, m, a, n, space, ^Y, enter. Upon exit, ^Y. > No way to set a command aside. ^A, ^K. Grab it again with ^Y. (Yes, these are all readline shortcuts. If you think they’re a bit long, bind them to something shorter in your inputrc.)

Do you actually use zsh? C-o and M-q and M-a and M-h and all the others are really nice, and as far as I know bash has nothing similar (correct me if I'm wrong). You don't NEED any of these niceties but they're very nice.

Re: Kali Linux 2020.3

#20

Post by Nullabillity »

enriquto wrote: post #16
daffy wrote: post #9

One nice thing in zsh is that you can type `/u/lo/b ` and be in `/usr/local/bin`.

Bash does the same thing here, typing tabs instead of slashes. /u lo b same number of keystrokes actually

Not quite. Zsh can use the subfolders to disambiguate which parent you meant, bash can't.
Post reply on HN