cultural reviewer and dabbler in stylistic premonitions

  • 12 Posts
  • 78 Comments
Joined 4 years ago
cake
Cake day: January 17th, 2022

help-circle




  • “But you can’t copy with Ctrl+C, it’s…” - You can. When something is selected It copies selection to clipboard, otherwise it sends SIGINT.

    What terminal emulator are you using where ctrl-c copies instead of sending SIGINT when text is selected? In every one I’ve ever used, ctrl-c still sends SIGINT even with text selected (and one must must use ctrl-shift-C/ctrl-shift-V to copy/paste).

    I don’t have any suggestion for getting the behavior you’re asking for, but besides the normal ctrl-(shift)-C/V clipboard FYI you also have two other types of clipboard-like things: one which works anywhere (not only in the terminal) and is actually always automatically copying anything you select and lets you paste from it with middle click (this originated with X Windows but i think most Wayland compositors have also implemented it by now), and another which is found in GNU Readline (used by bash and numerous other REPLs) called the “kill buffer” which can be pasted (or “yanked”) from and cut (or “killed”) to using Emacs keyboard shortcuts (which also include various cursor movement controls).

    Notes:

    • the kill buffer is local to a given readline context, it’s not shared across different shell windows.
    • the list of emacs keybindings in that wikipedia article i linked is currently confusingly referring to the kill buffer as “the clipboard”
    • you can drastically reconfigure your readline keybindings and other behavior by editing your .inputrc file, but you cannot achieve what you were originally asking for because there is no concept of text selection in readline.

    HTH!





  • How exactly do they hope to lock devs in github??? That’s absurd, there’s no way they can achieve that. I can always take my projects elsewhere and there’s nothing they can do to stop me.

    I can’t tell if you’re joking? If not, what do you think “lock-in” actually means?

    It doesn’t mean that it is impossible to leave, it means that there is substantial switching cost. And, that is certainly the case for github-hosted projects: all active contributors need to make a new account somewhere else, issues and discussions need to be migrated, CI workflows typically need to be rewritten, and good luck finding something that gives as much free compute for CI as github does. Yes, it’s easy to mirror a git repo onto another service, but github is much much more than just git repo hosting and each of their features have their own switching cost.

    Also, OP actually said “lock devs in” rather than “lock projects in” - I actually am forced to have a github account if i want to contribute to projects which refuse to move their issues off of it 😢 … and the difficulty in creating new accounts anonymously these days prevents me from contributing to several things (lemmy, for instance) which i otherwise would.













  • Arthur Besse@lemmy.mlMtoLinux@lemmy.mlWhat was Linux like in the 90s
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    8 months ago

    encryption would prevent the modem from seeing it when someone sends it, but such a short string will inevitably appear once in a while in ciphertext too. so, it would actually make it disconnect at random times instead :)

    (edit: actually at seven bytes i guess it would only occur once in every 72PB on average…)