• /home/pineapplelover@lemm.ee
    link
    fedilink
    arrow-up
    0
    ·
    3 months ago

    I refuse to see how vim and emacs is worth learning. I only use it because that’s the only option when editing server files. Beyond this, I couldn’t imagine coding in these environments from scratch.

    • I Cast Fist@programming.dev
      link
      fedilink
      arrow-up
      1
      ·
      3 months ago

      I only use it because that’s the only option when editing server files.

      suggestion 1: use nano. Unlike vi(m) and emacs, it’s meant for humans, all the command shortcuts you can execute are listed at the bottom.

      suggestion 2: browse the servers in question via your file explorer (sftp://user@server or just sftp://server) of choice or WinSCP if you’re on windows, open whatever file with your local graphical text editor of choice.

    • KubeRoot@discuss.tchncs.de
      link
      fedilink
      English
      arrow-up
      1
      ·
      3 months ago

      By the way, for editing server files consider nano. It’s also widely available, has simpler shortcuts and displays them on the screen. It’s obviously not powerful like vim, but a good match when you just need to edit a config file.

      • 1rre@discuss.tchncs.de
        link
        fedilink
        arrow-up
        0
        ·
        3 months ago

        Nano is just as fiddly as vim and way less powerful when you actually figure out what you’re doing though?

        Ie a completely redundant piece of software that has no place being pre-installed anywhere

    • Hexarei@programming.dev
      link
      fedilink
      arrow-up
      0
      ·
      3 months ago

      The biggest benefit of (neo)vim is the motions.

      Honestly if you don’t use vim motions in your ide of choice, you’re missing out big time. Being able to do things like “Delete everything inside these parentheses”. di( or “wrap this line and the two lines below in a pair of {}” ys2j{ , or “swap this parameter with the next one” cxia]a. with a single shortcut is game changing.

      Even just being able to repeat an action a number of times is ridiculously useful. I use relative line numbers, so I can see how many lines away a target is and just go “I need to move down 17 lines” and hit 17j.

      Absolutely insane how much quicker it is too do stuff with vim motions than ctrl-shift-arrows and the like.

      • FizzyOrange@programming.dev
        link
        fedilink
        arrow-up
        0
        ·
        3 months ago

        Honestly those things just don’t sound like common enough actions to be worth shaving 0.5 seconds off. How often do you know exactly how many lines to move a line by? And how often do you even need to move a line that far?

        I still don’t buy it.

        • pearable@lemmy.ml
          link
          fedilink
          arrow-up
          0
          ·
          3 months ago

          Relative lines means each line except the one your cursor is on is relative to your current line. Like this:

          5 5k jumps here

          4

          3

          2

          1

          6 your cursor is here

          1

          2

          3

          4

          5

          6

          7

          8 8j jumps here

          The main reason I like it is I don’t like mouse ergonomics. Keeping my hands on the keyboard just feels better

          • FizzyOrange@programming.dev
            link
            fedilink
            arrow-up
            1
            ·
            3 months ago

            Yes I understood that. My point is how often do you know you need to move a line exactly 17 lines? Do you count them? Clearly much slower than doing it interactively by holding down ctrl-shift-down for a bit.