<story><title>Kali Linux 2020.3</title><url>https://www.kali.org/news/kali-2020-3-release/</url></story><parent_chain><item><author>idoubtit</author><text>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:&lt;p&gt;- 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.&lt;p&gt;- 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.&lt;p&gt;- 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.&lt;p&gt;- No way to pause a command and view the man. With zsh, `git clone&amp;lt;alt-h&amp;gt;` will display `man git-clone`, then return to the incomplete command line.&lt;p&gt;- No way to set a command aside. E.g. if I realise while typing that I&amp;#x27;m not in the right directory, `git clone&amp;lt;alt-q&amp;gt;cd src&amp;lt;return&amp;gt;`.</text></item></parent_chain><comment><author>mkl</author><text>&amp;gt; - The history is editable by default. If I move to a previous history line and change it, the old line disappears.&lt;p&gt;Press M-r to revert back to the original command.&lt;p&gt;&amp;gt; - No way to set a command aside. E.g. if I realise while typing that I&amp;#x27;m not in the right directory, `git clone&amp;lt;alt-q&amp;gt;cd src&amp;lt;return&amp;gt;`.&lt;p&gt;Press M-# to comment out the current command and go to a new prompt, then up to get the commented command back, and M-3 M-# to uncomment it and run it (any number works, but 3 is the same key as #).</text></comment>
<story><title>Kali Linux 2020.3</title><url>https://www.kali.org/news/kali-2020-3-release/</url></story><parent_chain><item><author>idoubtit</author><text>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:&lt;p&gt;- 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.&lt;p&gt;- 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.&lt;p&gt;- 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.&lt;p&gt;- No way to pause a command and view the man. With zsh, `git clone&amp;lt;alt-h&amp;gt;` will display `man git-clone`, then return to the incomplete command line.&lt;p&gt;- No way to set a command aside. E.g. if I realise while typing that I&amp;#x27;m not in the right directory, `git clone&amp;lt;alt-q&amp;gt;cd src&amp;lt;return&amp;gt;`.</text></item></parent_chain><comment><author>codetrotter</author><text>&amp;gt; E.g. if I realise while typing that I&amp;#x27;m not in the right directory, `git clone&amp;lt;alt-q&amp;gt;cd src&amp;lt;return&amp;gt;`.&lt;p&gt;With bash I’d just Ctrl+a and type “cd src ;” and then press ctrl+e and continue typing what I was typing.&lt;p&gt;I got so used to doing it that way, that even after switching to zsh I still do it this way.&lt;p&gt;The disadvantage of my way of doing it is if you typo the path. But I tab complete pretty much always, so in practice I don’t have the problem of typoing directory names without noticing.&lt;p&gt;I probably should learn those zsh ways of doing things. Will try to remember to do it the zsh way next time I need to do something like the things you mentioned.</text></comment>