3 ms·

macOS’s terminal app does #1 but you have to option-click. It’s kind of a hack too, it just issues a bunch of right/left arrow key codes to the shell to move yo

macOS’s terminal app does #1 but you have to option-click. It’s kind of a hack too, it just issues a bunch of right/left arrow key codes to the shell to move your cursor to the designated spot. Your second point is definitely my #1 issue, at least it is on Linux and Windows (macOS at least uses Cmd-c everywhere and it works.) I have to constantly remember to use ctrl-shift-c to copy in the terminal but ctrl-c to copy everywhere else, and I constantly forget and use ctrl-shift-c in a not-terminal program, and do something stupid like open dev tools in chrome, ugh. This is, unfortunately, not fixable. Not without rewriting every app on my system to use a different copy/paste combo.

eviks 2y ago
Wait, what do you mean not fixable when you can just change the keybind in the terminal app to use ctrl-c to copy?
- ninkendo 2y ago
  Ctrl-C is SIGINT, I don’t want to change its definition of sigint just to make room for copy behavior. What I want is to make a different shortcut trigger copy/paste, everywhere, and that’s not fixable. Every app independently decides to make ctrl-c implement copy, so changing that is basically not possible.
  - eviks 2y ago
    You don't need to change the definition of sigint, just its shortcut! Though it's also possible to fix it everywhere - use a keyboard rebinding tool to make Ctrl-Shift-C send Ctrl-C key combo instead
    - ninkendo 2y ago
      > You don't need to change the definition of sigint, just its shortcut! That’s what I mean? Changing sigint’s shortcut isn’t what I want to do. > Ctrl-Shift-C send Ctrl-C key combo instead Then ctrl-shift-C will send SIGINT too, and I’m back to where I started (SIGINT and copy having the same shortcut)
      - eviks 2y ago
        > That’s what I mean? I'm sorry, I thought there might've been some confusion re. actual sigint definition based on some deeper history and ASCII codes (which didn't seem like it from cursory search) > ctrl-shift-C will send SIGINT You filter against your terminal app, where Ctrl+Shift+C will continue send Ctrl+Shift+C
p0w3n3d 2y ago
Agree, MacOS terminal has this distinction between Control which is purely terminal modifier, and Command which is purely Mac modifier, hence when I work in terminal on MacOS I do CMD+C - CMD+V and this is consistent with all the other apps, while on Linux you have to either think of CTRL+C as a copy or as a SIGINT, depends on which app you are using. This was so good experience for me, that I reconfigured my Linux terminal to have Win+C, Win+V and Win+T (for new tab). However this is inconsistent with Linux window management. Since then I have been actively looking for a way to change the Linux OS manager to have default global hotkeys in the MacOS style. Anybody knows how to do that? ( https://news.ycombinator.com/item?id=41439601 https://news.ycombinator.com/item?id=41439601 - suggested xmodmap is a key mapping way which will break my CTRL+C in terminal )
- p0w3n3d 2y ago
  while writing this I found https://github.com/rbreaves/kinto https://github.com/rbreaves/kinto - I need to give it a try as this (hopefully) is not simple overlay for xmodmap...

eviks 2y ago

Wait, what do you mean not fixable when you can just change the keybind in the terminal app to use ctrl-c to copy?

ninkendo 2y ago
Ctrl-C is SIGINT, I don’t want to change its definition of sigint just to make room for copy behavior. What I want is to make a different shortcut trigger copy/paste, everywhere, and that’s not fixable. Every app independently decides to make ctrl-c implement copy, so changing that is basically not possible.
- eviks 2y ago
  You don't need to change the definition of sigint, just its shortcut! Though it's also possible to fix it everywhere - use a keyboard rebinding tool to make Ctrl-Shift-C send Ctrl-C key combo instead
  - ninkendo 2y ago
    > You don't need to change the definition of sigint, just its shortcut! That’s what I mean? Changing sigint’s shortcut isn’t what I want to do. > Ctrl-Shift-C send Ctrl-C key combo instead Then ctrl-shift-C will send SIGINT too, and I’m back to where I started (SIGINT and copy having the same shortcut)
    - eviks 2y ago
      > That’s what I mean? I'm sorry, I thought there might've been some confusion re. actual sigint definition based on some deeper history and ASCII codes (which didn't seem like it from cursory search) > ctrl-shift-C will send SIGINT You filter against your terminal app, where Ctrl+Shift+C will continue send Ctrl+Shift+C

p0w3n3d 2y ago

Agree, MacOS terminal has this distinction between Control which is purely terminal modifier, and Command which is purely Mac modifier, hence when I work in terminal on MacOS I do CMD+C - CMD+V and this is consistent with all the other apps, while on Linux you have to either think of CTRL+C as a copy or as a SIGINT, depends on which app you are using. This was so good experience for me, that I reconfigured my Linux terminal to have Win+C, Win+V and Win+T (for new tab). However this is inconsistent with Linux window management. Since then I have been actively looking for a way to change the Linux OS manager to have default global hotkeys in the MacOS style. Anybody knows how to do that? ( https://news.ycombinator.com/item?id=41439601 https://news.ycombinator.com/item?id=41439601 - suggested xmodmap is a key mapping way which will break my CTRL+C in terminal )

p0w3n3d 2y ago
while writing this I found https://github.com/rbreaves/kinto https://github.com/rbreaves/kinto - I need to give it a try as this (hopefully) is not simple overlay for xmodmap...