On Linux, Control-C and Control-V don't work for copying and pasting in terminals. The Control modifier is used for its original purpose of inserting control codes. Instead, terminal apps require an extra Shift modifier, like Control+Shift+C. But what if there were hidden shortcut combos for copy and paste
  • glitchdx@lemmy.worldEnglish
    41·
    2 months ago

    I was just complaining about something like this just the other day.

    edit: hold on, they want me to have dedicated keyboard keys for copy and pasta? No. I am not accepting that as a solution.

        • brian@programming.dev
          2·
          2 months ago

          yeah, if you bind ctrl c and ctrl v to copy and paste keys, you can get the same behavior in terminals and other apps that have weird default bindings for ctrl c and v for historical reasons

  • ertai@programming.dev
    3·
    2 months ago

    I don’t understand why they mention programmable keyboards there. Buying a programmable keyboard to be able to rebind your keys is silly when it can be made entirely through software. On X11 for example you can load a .Xkeymap file and set your keyboard mappings this way. I use this to have a modified dvorak keymap with Altgr+auoeidhtns giving [(=+)]] on the home row for instance, very convenient. Then I use my window manager i3 to rebind mod+p to send Ctrl+V using xdotool (because mod+p seems more vim-like) and I’ve set my terminal urxvt to treat Ctrl+V as paste. if all software supported the Sun copy paste keys then I could send those keys instead of Ctrl+V.

    • brian@programming.dev
      1·
      2 months ago

      it is nice to be able to plug your keyboard into a new computer and have all your shortcuts and layout set up though. I do that so I have the same layout and shortcuts on my personal and work computers regardless of os

    • ulterno@programming.devEnglish
      1·
      2 months ago

      Interesting:

      [{(|=+\)]}]

      [(=+)]]

      So there is {<text1>|<text2>} to get <text1><text2>.

      What to do to get text2 under the mainline text1 instead?

      And is this part of Markdown or some other parsing? How come I missed it?