I read a lot of answers online that its a bad idea, but the arguments did not make a lot of sense. “it’s a heavily ingrained part of the eco system”. Well if I can change it, what’s the deal?

It makes more sense to make an interrupt signal be the harder shortcut, and copy to be ctrl+C, matching other programs and platforms.

  • taladar@sh.itjust.works
    28·
    10 months ago

    It is a bad idea to get used to using Ctrl+C as copy on the terminal because then you will accidentally abort programs all over with muscle memory on systems you haven’t twisted beyond recognition customized.

    • matcha_addict@lemy.lolOP
      9·
      10 months ago

      That’s a valid point. I already have a similar but not exactly the same problem when I move between linux and macos, where the shortcuts don’t really match or work.

      The difference between ctrl+C on the browser and ctrl+C on the terminal already disorients me. I’d rather the shortcut work the 99% of the time I’m on my own machines.

      I think I’ll just have to really keep this in mind when not using my own machine.

      • atzanteol@sh.itjust.worksEnglish
        1·
        10 months ago

        I used to create tons of aliases and custom helper scripts. It became a real pain whenever I worked on a Linux server or something that didn’t have all my customizations. Now I only have one alias (l=“ls -Fhla”). Getting used to my snowflake system just made things more complicated for me…

    • beirdobaggins@lemmy.world
      6·
      10 months ago

      I use the terminal so much that I frequently accidentally use Ctrl-Shift-C and V outside of the terminal.

      Ctrl-Shift-V usually works pretty well as it does a paste without formatting in a lot of places.

      Accidentally hitting Ctrl-Shift-C though in a MS Team’s chat though, starts a voice call with all chat participants. 😑 hate it