zsh

This is not a feature of rsync, but of your shell. So the question "does rclone have that" doesn't make much sense, because it usually wouldn't be rclone implementing it. For example, zsh does it here for rsync, which actually invokes `ssh` itself: https://github.com/zsh-users/zsh/blob/3e72a52e27d8ce8d8be0ee... https://github.com/zsh-users/zsh/blob/3e72a52e27d8ce8d8be0ee... That said, some CLI tools come with tools for shells to help them implement such things. E.g. `mytool completion-helper ...` But I don't get rclone SSH completions in zsh, as it doesn't call `_remote_files` for rclone: https://github.com/zsh-users/zsh/blob/3e72a52e27d8ce8d8be0ee...

> Is it possible that zsh behavior changes when those are triggered? It doesn't look that way, at least looking at the option handling code in the read builtin (bin_read): https://github.com/zsh-users/zsh/blob/8a3ee5a/Src/builtin.c#...

Somewhat predictably zsh also has a digraphs¹ feature, via the insert-composed-char function². Supported characters can be seen in source³, and beyond that there is the insert-unicode-char² function for when you need it. I flit between regular compose key input and zsh/vim digraphs in a way that makes no sense to me whatsoever. Compose ^1, AltGr+1 or C-k 1S all kind of feel natural to me, but the advantage of the ZLE method is that you can also use it to preview characters which can be useful if you want to test something out while in another widget or find the hex value to insert using some other tool. ¹ https://datatracker.ietf.org/doc/html/rfc1345#section-2.3 ² https://zsh.sourceforge.io/Doc/Release/User-Contributions.ht... ³ https://github.com/zsh-users/zsh/blob/master/Functions/Zle/d...

Zsh users get a bundled curses module; see zsh/curses¹ in zshmodules(1). It is a very thin wrapper, so it works how you'd expect from other uses. There is a tetris implementation using zsh/curses that ships with zsh², and you can use it as a nice comparison to the non-curses implementation that also comes with zsh³. I've used zsh/curses a few times to hack together little interfaces, and it is quite workable. It makes things far simpler once you start reaching for terminfo's capabilities that require you to think about state too much. A friend of mine wrote a little mblaze⁴ frontend using it, and it felt like using single mailbox mutt with less than a hundred lines of code. I was expecting the linked project to be a loadable module too given that bash also supports them, but it is actually a little more interesting to look at given it

That's pretty cool, gonna steal the idea. I can implement that specific case with a couple of lines in zsh. Something like: autoload -Uz zed icommit() { () { zed $1 git commit -F $1 # -a too, if you must ;) } =(:) # Or maybe even =(< commit_template.txt) } Then icommit, via zed¹, will initiate an inline editor with all the power of ZLE available. Hit C-x C-w to write and commit, or C-c to abort. Obviously, you'd want some error checking and the like². Beauty of this basic implementation is that the keymap is fully controllable in zed as it is simply a new ZLE widget. It works with emacs or vi mode out of the box, and is fully customisable beyond that. You could make the interface generic by writing your own ZLE widget, so that it can be called directly from within the line editor and remove t

> Now, listen. I wish I could continue here and end with “… and this is why ZSH does it that way!” https://github.com/zsh-users/zsh/blob/47c7bc9b1493c7374f076b... has a comment about this behaviour, but no justification. I think it's just an optimization to save a little bit of time by not forking, and to avoid having the zsh process hanging around taking resources for no reason.

I fixed that bug in zsh two years ago. It got released in zsh 5.9. https://github.com/zsh-users/zsh/commit/326d9c203b3980c0f841... I'm going to be answering questions about it until my dying day.

You need to upgrade to zsh 5.9, or backport the patch I sent them two years ago: https://github.com/zsh-users/zsh/commit/326d9c203b3980c0f841... If you can't upgrade zsh, then the workaround is to say `sh -c ./ape-program` or `bash -c ./ape-program` instead of `./ape-program`.

You need to upgrade to zsh 5.9, or backport the patch I sent them two years ago: https://github.com/zsh-users/zsh/commit/326d9c203b3980c0f841... If you can't upgrade zsh, then the workaround is to say `sh -c ./ape-program` or `bash -c ./ape-program` instead of `./ape-program`.

While I was reading Julia Evan's "Behind "Hello World"[0] on Linux, I had some fun digging up the zsh[1] source code. Granted, I needed some help from Cody AI[2] and even wrote some notes from my learning https://blog.yelinaung.com/posts/behind-hello-world-on-linux... [0]: https://jvns.ca/blog/2023/08/03/behind--hello-world [1]: https://github.com/zsh-users/zsh [2]: https://docs.sourcegraph.com/cody

patched ca. zsh 5.8: https://github.com/zsh-users/zsh/commit/326d9c203b3980c0f841...

[Original finder here; I wrote that, I checked.] See the docs: https://github.com/zsh-users/zsh/blob/f8d93888a8efd6c8142e74... Relevant code: https://github.com/zsh-users/zsh/blob/f8d93888a8efd6c8142e74...

It was merged: https://github.com/zsh-users/zsh/commit/326d9c203b3980c0f841... We patched fish too! Plus NetBSD sh and FreeBSD sh.

Try upgrading to the latest version; I upstreamed a patch in zsh last year. https://github.com/zsh-users/zsh/commit/326d9c203b3980c0f841...

So can Zsh -- this functionality has shipped with Zsh since for several years, though not enabled by default. See https://github.com/zsh-users/zsh/blob/master/Functions/Zle/b... or https://github.com/zsh-users/zsh/blob/master/Functions/Zle/b...