pip in Zsh
Last updated on August 8, 2017
Pip is a package management system for installing and managing Python software packages. To enable auto completion for pip in zsh, the documentation of pip suggests adding the following line to ~/.zshrc:
eval "`pip completion --zsh`"However, merely having this line would not enable auto completion for pip3. To enable auto completion for pip3 as well, add the following line after the line above:
compctl -K _pip_completion pip3ls Command
Last updated on April 14, 2024
The ls command is a command to list files on a UNIX-like system. It is probably one of the most used command. However, a plain ls command without any polishing may look really “plain”. Here, we will slightly configure this command to make it more usable:
Screenshots:
Output of ls before configuration
Output of ls after configuration
Pagination for ls
Last updated on December 10, 2016
In both bash and zsh, there are multiple methods to check whether a command exists. In this post, a set of speed tests will be performed on them to find the fastest way in each of the two shells (NOT to compare the two shells). We will test 5 different methods (foobar is the command to test for existence in the list):
type foobar &> /dev/nullhash foobar &> /dev/nullcommand -v foobar &> /dev/nullwhich foobar &> /dev/null(( $+commands[foobar] )) (zsh only)All the methods listed above will have a return status of zero if the command foobar exists, otherwise non-zero. That is, after replacing testing-command by any of the commands listed above, you can test the existence of the command foobar by executing testing-command && echo exist || echo non-exist.
Throughout this post, ls will be the command that is used for testing existence, which does exist on the system which runs the tests. The test environment is Debian Jessie with bash 4.3.30 and zsh 5.0.7 on Intel Xeon processor E3-1240 v3 (8 MB Cache, 3.4 GHz). The test scripts are also available at the end of the post.
Last updated on December 10, 2016
In zsh, it is often annoying that we can't easily restore the command we just canceled by Ctrl-C: canceled commands are not recorded into the history file and thus cannot be restored by searching previous commands. To make the restoration possible, zsh provides a variable ZLE_LINE_ABORTED which keeps a record of the last command that was canceled—everything looks so simple. However, for some reasons, such as canceling stuck tab completion, we often push Ctrl-C for more than once—but ZLE_LINE_ABORTED would become empty if Ctrl-C is used on an empty line! Thanks to the great extensibility of zsh, we can solve this issue by tweaking zle-line-init (add the following to your ~/.zshrc):
function zle-line-init {
# Your other zle-line-init configuration ...
# Store the last non-empty aborted line in MY_LINE_ABORTED
if [[ -n $ZLE_LINE_ABORTED ]]; then
MY_LINE_ABORTED="$ZLE_LINE_ABORTED"
fi
# Restore aborted line on the first undo.
if [[ -n $MY_LINE_ABORTED ]]; then
local savebuf="$BUFFER" savecur="$CURSOR"
BUFFER="$MY_LINE_ABORTED"
CURSOR="$#BUFFER"
zle split-undo
BUFFER="$savebuf" CURSOR="$savecur"
fi
}
zle -N zle-line-initzle-line-init widget which will be executed every time when the a new command line is ready to take input.ZLE_LINE_ABORTED is non-empty, save it to MY_LINE_ABORTED.MY_LINE_ABORTED is non-empty, the initial undo will restore the contents in MY_LINE_ABORTED. Also see man zshzle for an explanation of split-undo.zle-line-init.Now type any command and push Ctrl-C twice and undo (bound to Ctrl-/ by default): your canceled command is back!
Note that if you use zsh-autosuggestions this code snippet somehow breaks it. Adding _zsh_autosuggest_widget_clear before the end of zle-line-init would fix it.