So found this issue because I have started to move to linux from windows and I've been trying different terminal emulators but I hadn't really found any yet that support ctrl+c for copy and terminating commands like Windows has the option to (am trying the elementary terminal now, didn't know it had that). But as far as I'm concerned there doesn't seem to be a good way to implement this and it seems like a shallow UX improvement that would actually make things worse if you actually look more into it. If there's any better idea to handle this cleanly without running into any of the issues I've mentioned, please let me know. I feel like this wouldn't solve an issue that doesn't exist. People are used to ctrl+shift+c, it works, if you want to press less keys, you can bind the copy and paste keys (which are bound by default). But thinking about the benefits, there doesn't seem to be enough to support this change. Building it into Alacritty will always require some special workaround which might affect users unrelated to this feature and it could contribute to a lot of 'weird' heuristics thrown around the codebase. So this isn't straight-forward and I do not think there are any good ways to handle it. And if you set it up so it only works when the selection is visible, then users will get confused again. An invisible selection thousands of lines away in the scrollback buffer could be the sole reason why copy/pasting isn't working anymore. So there's no reason why a selection would have to be visible for Ctrl+C not to work. Now Alacritty does support a scrollback buffer though.
This could of course be fixed by not setting it as a default, but then there's a need to document it so people actually know about it. Would Alacritty configure Ctrl+C as the default for copy/pasting inside the terminal, then a lot of people used to terminal emulators could get really, really confused. My first issue is mostly about element of least surprise. I think this is a really bad idea and there are a couple of reasons that play together why I think it is.
0 kommentar(er)
