select-quoted is also useful with a number of other characters, all of the following are useful {a,i}"${(s..):-\'\"\|,./:;-=+@}`

There’s also a select-bracketed for things like i(, i{, i< which you don’t seem to use. And surround is also available.

I’m not a huge fan of cdpath myself; I tried it for a while a few years ago and found it too “magic”, especially once you start adding a whole bunch of directories in there. Same with autocd btw; I toggled between having that on and off way back in my tcsh days, and eventually decided that explicitly typing commands isn’t too much of a burden. But yeah, if that works for you: 👍 One of the nice things of zsh is that it gives you plenty of tools to do things the way you want; these are just some things I find useful personally but hadn’t seen much in other articles (which is why it excludes e.g. “show git branch in prompt”, as there are already 600 articles on that).

Personally I find “start with ” almost always a much more useful way to search. Searching for ls also matches alsamixer, tools, tls, totals, docker ls, and probably a bunch of other things. Usually I know what I want (history for a specific command), and the computer is generally dumber than me for these kind of things on account of not being able to read my mind. I never quite understood how anyone can deal with things like “fuzzy searches” btw.

What does that (N) do? I can’t seem to find any docs on it, and it doesn’t seem to behave quite the same?

[~]% ls -ld /bin /usr/bin
lrwxrwxrwx 1 root root     7 Apr  6 15:36 /bin -> usr/bin/
drwxr-xr-x 2 root root 57344 May 22 15:38 /usr/bin/

[~]% path=(/bin(N) /usr/bin(N))
[~]% echo $path
/bin /usr/bin

[~]% path=() 
[~]% _postpath /bin
[~]% _postpath /usr/bin
[~]% echo $path
/usr/bin

Ah, thanks; I’ll update the _exists and _{pre,post}path functions.

To be honest I never really looked much at zle, and always found it a bit confusing. I need to sit down and properly look at it one day. There’s some other useful stuff in that zshrc as well btw (like using terminfo instead of bindkey '^[OA').

For sudo, I am using this version:

# Meta-S will toggle sudo
function vbe-sudo-command-line() {
    [[ -z $BUFFER ]] && zle up-history
    if [[ $BUFFER == sudo\ * ]]; then
        LBUFFER="${LBUFFER#sudo }"
    else
        LBUFFER="sudo $LBUFFER"
    fi
}
zle -N vbe-sudo-command-line
bindkey "\es" vbe-sudo-command-line

For _postpath, it could be further simplified to (relying on Zsh not doing word-splitting by default and arrays are not nested:

_postpath() {
    for dir in "$@"; do
        dir=${dir:A}
        [[ ! -d $dir ]] && return
        path=($path $dir)
    done
}

I don’t rely on typeset -U myself as it can be fooled with symlinks (and I want to keep symlinks in path, notably for the path to Nix profile). So, I do the dupe checks manually: https://github.com/vincentbernat/zshrc/blob/master/zshenv#L28

Oops, should be fixed now; forgot to add a line when linking to this thread. “I’ll just make this simple change real quick, no need to test locally”.

push-line is pretty neat and didn’t know about it. I ended up doing it like this:

remember() {
	# Nothing in buffer: get previous command.
	if [[ $#BUFFER -eq 0 ]]; then
		print -ln "${stored:-}"
		stored=
	# Store current input.
	else
		stored=$BUFFER
		BUFFER=
	fi
}
zle -N remember
bindkey '^Q' remember

It’s essentially the same, except that you need to explicitly put the pushed value back with a second ^Q press, which seems a bit nicer to me.

A related thing I found/added btw:

# Run command but don't clear commandline and preserve cursor position.
bindkey '^\'    accept-and-hold

Which seems pretty useful when mucking about with longer curl command etc.

Note that push-line is already mapped to M-q by default.

Oh yeah, you’re right. readlink is not always installed by default on Linux either (on some distros it’s a separate package, I forgot which one, and perhaps that changed now since I encountered this >5 years ago). It’s worked on all systems I’ve used in the last ~2 years though (including busybox), so it’s “good enough” for me 😅

As I understand it, wd is a “super-charged cd”, whereas with hash -d it works everywhere and you can do stuff like vim ~x/foo and cp ~x/foo . etc.