• Danny M@lemmy.escapebigtech.info
    12·
    1 year ago

    I prefer the extremely intuitive:

    [C-R]=system("grep -P "PPid:\t(\d+)" /proc/$$/status | cut -f2 | xargs kill -9")

    or

    i:!grep -P "PPid:\t(\d+)" /proc/$$/status | cut -f2 | xargs kill -9[esc]Y:@"[cr]

    It just rolls off the fingers, doesn’t it?

    Edit: damn it lemmy didn’t like my meme because it assumes that characters between angle brackets are html tags :( you ruined it lemmy

    EDIT 2: rewrote it, just assume that square brackets are buttons not characters

  • aard@kyu.de
    9·
    1 year ago

    I always get annoyed when I’m on some system and nano pops up and I need to figure out how to kill that thing.

      • aard@kyu.de
        48·
        1 year ago

        It shows a message which wastes valuable screen estate, especially on low resolution terminals, containing a message I have to read every single time because the keys are not in muscle memory, and never will because the bindings are stupid.

        On systems I have control over the reaction to nano popping up is exiting, removing it, making sure the package system blocks reinstallation attempts, and go back to what I was initially doing in a sane editor.

        • nixcamic@lemmy.world
          0·
          1 year ago

          My man, most of us aren’t connecting to our mainframes on VT20s these days. Even on my phone screen the three extra lines nano takes over vi aren’t a problem.

          Also if you have the time to go through all that you have the time to learn ctrl+x.

  • Doctor xNo@r.nfEnglish
    7·
    1 year ago

    There’s a button to exit vim on your pc. Just hold it 7 seconds and vim is closed. 😅

    • 0x4E4F@sh.itjust.worksEnglish
      01·
      1 year ago

      When you know how to exit, you just slap your face 🤦 and ask “why… why, please, why don’t they add new shortcuts 🤦!”.

      • mvirts@lemmy.world
        0·
        1 year ago

        Lol if you know how to exit, you may know that you actually can change almost everything about vim.

        • 0x4E4F@sh.itjust.worksEnglish
          01·
          1 year ago

          I don’t think you can add modifier keys in shortcuts.

          And this behavior should come out of the box, not me changing stuff around so I can make it usable. For something that I use all the time, sure, but I only use a terminal text editor with git, and I don’t use git that often. For everything else, I use a GUI text editor (mousepad, leafpad, whatever).

  • LainOfTheWired@lemy.lolEnglish
    1·
    1 year ago

    Wouldn’t you want to just want to type q! As you’ve probably opened it and accidentally made changes you didn’t want to. So you wouldn’t want to save the config file. Or the text file you just created.

      • lars@lemmy.sdf.org
        1·
        1 year ago

        :x was a gamechanger. And it doesn’t update the file’s modify date if you made no changes.

        Sometimes I just sit back and think about all that saved time and effort so much that I have actually lost time by switching from :wq.

      • rwhitisissle@lemmy.world
        1·
        1 year ago

        Because :wq to me means “Issue command write, followed by command quit.” “Issue command x” to me means nothing in the context of vim, and ctrl + x on most systems is reserved for cutting, so it just “feels” wrong.

    • raptir@lemdro.idEnglish
      1·
      1 year ago

      If anything it is dangerous as it will still exit even if changes cannot be saved.

  • JackGreenEarth@lemm.eeEnglish
    1·
    1 year ago

    I’ve never understood people arguing about terminal text editors like nano and vim. Why not just use a GUI text editor like gedit?

    • EarthlingHazard@lemm.ee
      3·
      1 year ago

      I’m not the most Linux savvy but when I ssh onto a work machine I’ll use a terminal editor instead of copying the file onto a local machine, editing the file in a GUI and then overwriting the file on the remote machine

  • JGrffn@lemmy.world
    0·
    1 year ago

    Serious question. Why? No, for real, why? Why are these hard to understand editors still the default on most distros and flavors? Why haven’t they reinvented themselves with easier to understand shortcuts?

    I get the feeling my comment will attract heat, but I’m a web dev, studied comp Sci for years, have worked for nearly a decade and have spent over half my 30 year old life using computers of all sorts. I’m by no means a genius and I by no means know enough about this or most tech subjects, but I literally only knew how to close vim with and without saving changes in a recent vim encounter, purely due to a meme I saw in this community a few days prior, and I had already forgotten the commands by the time I saw this post. Nothing about vim and alternatives feels intuitive or easy to use, and you may say it’s a matter of sitting down and learning, which you can argue that, but you can’t argue this isn’t a bit of a gatekeeper for people trying to dip their toes into anything that could eventually rely on opening vim to do something.

    I won’t try to deny its place in computer history, or its use for many, or even that it is preferred by some, but when every other software with keyboard shortcuts agrees on certain easy to remember standards, I don’t quite understand how software that goes against all of that hasn’t been replaced or hasn’t reinvented itself in newer versions.

    Then again, I have no idea what the difference between vi, vim, emacs, and nano are, so roast away!

    • voidMainVoid@lemmy.world
      1·
      1 year ago

      Some people like vim the way it is. That’s why they haven’t re-invented it. If you want to use a more intuitive text editor, there are plenty available (such as nano or micro).They don’t need to turn vim into a clone of something that already exists.

      As for why it’s still the default… It’s the same reason why everybody uses QWERTY keyboards when Dvorak is clearly superior. People already know how to type with QWERTY and they don’t want to take the time to re-learn with a new layout, change their workflows, etc.

      It isn’t universal, though. Garuda Linux defaults to micro. The web dev boot camp I was in didn’t bring vim up at all! We only used nano! I think that was a disservice to the students, but the instructors must’ve thought that it would be too confusing.