• macniel
    link
    fedilink
    367 months ago

    GNU nano is a nice easy text editor… but it’s so clunky when you have become comfortable with vim (perhaps the same with Emacs).

    • LeoOPA
      link
      fedilink
      817 months ago

      The trick is to never get comfortable with Vim or Emacs.

      *taps forehead*

    • @thehatfox@lemmy.world
      link
      fedilink
      English
      307 months ago

      Using nano as a vim user is a lot less clunky than trying to use vim as a vim non-user though.

      Or so I would imagine, all of the vim novices are still too busy trying to exit vim to share their experiences.

      • @evatronic@lemm.ee
        link
        fedilink
        English
        77 months ago

        The worst and best thing you can do when using vim is learn the movement keys (h, j, k, and l) because they’re so powerful and work no where else.

            • @laurelraven@lemmy.blahaj.zone
              link
              fedilink
              17 months ago

              Okay, perhaps I should have been clearer, that’s on me.

              I meant qwerty and related layouts.

              Things like Dvorak and Colemak, the movement keys are spread across the keyboard and if you want to navigate that way you’ll pretty much have to remap them, and probably remap the keys you’ve swapped. For me, it’s just easier to use the arrows than go through that.

              • @PlexSheep@infosec.pub
                link
                fedilink
                17 months ago

                I mean, yeah, of course. Vims default keys are made for the “regular” layouts. But you can Mal everything yourself if needed. I’m sure there are pre made mappings for other layouts too.

                • @laurelraven@lemmy.blahaj.zone
                  link
                  fedilink
                  27 months ago

                  I might check that out

                  Using the arrows may not be the most efficient, but I’m not spending enough time in vim to make that be an issue… Though I’ve seriously considered trying to swap to it from VSCode

                  • @PlexSheep@infosec.pub
                    link
                    fedilink
                    17 months ago

                    I do pretty much all editing in vim. One you “force” yourself to use hjkl, there was no going back to arrow keys. Nowadays I Mal arrow keys to move lines up and down and add or remove indentation.

    • Lung
      link
      fedilink
      87 months ago

      Neat that it has this new modern binds mode where it understands normal copy paste and stuff

      • Ada
        link
        fedilink
        English
        77 months ago

        I’m a little bit excited by that

    • @iiGxC@slrpnk.net
      link
      fedilink
      27 months ago

      Also worth checking out helix editor. Once you do the tutorial it makes vim feel clunky

    • @john89@lemmy.ca
      link
      fedilink
      17 months ago

      I think nano is good for quick and dirty editing.

      Anything else should be done locally on your development machine with a GUI, then pushed to your server as an update.

      • Kushan
        link
        fedilink
        English
        77 months ago

        Yeah I love nano. I can use vim a little, enough to make a change and save the output. I can even exit vim!

        But 9 times out of 10 if I need to edit a text file in a terminal window, I’m just making a quick config change - I need the terminal equivalent to notepad, not the terminal equivalent to an IDE.

        Nano is exactly what I need, nothing more and nothing less.

    • DefederateLemmyMl
      link
      fedilink
      English
      -4
      edit-2
      7 months ago

      apt purge nano is one of the first things I do on a new Debian installation. Much easier to remember than having to use update-alternatives, select-editor and the $EDITOR variable to convince the likes of vigr,vipw, visudo,crontab -e,… that I really want to use vim as my primary editor.