What a pile of ugly hacks. The only real problem I see is in sharing clipboard to/from ssh sessions, the rest is just self-inflicted by using programs with poor design. I could understand why a text editor would keep its own clipboard, but I don’t see a good reason why tmux and zsh need to have one as well.
Also the clipboard attack (and defense) seems overblown. Either you trust the source and you can paste code happily, or you don’t and then you better be extremely careful about what you’re executing from them. Bracketed paste is just not going to cut it, it’s trivial to hide malicious commands in a shell script.
The “poor design” is a historical artifact of using terminals. tmux and zsh have their own because there is no guarantee they are going to be used in an integrated environment: they may be that integrated environment. (Consider: running a machine without a GUI at all.)
What a pile of ugly hacks. The only real problem I see is in sharing clipboard to/from ssh sessions, the rest is just self-inflicted by using programs with poor design. I could understand why a text editor would keep its own clipboard, but I don’t see a good reason why tmux and zsh need to have one as well.
Also the clipboard attack (and defense) seems overblown. Either you trust the source and you can paste code happily, or you don’t and then you better be extremely careful about what you’re executing from them. Bracketed paste is just not going to cut it, it’s trivial to hide malicious commands in a shell script.
Isn’t this modern computing in a nutshell? ;)
The “poor design” is a historical artifact of using terminals. tmux and zsh have their own because there is no guarantee they are going to be used in an integrated environment: they may be that integrated environment. (Consider: running a machine without a GUI at all.)