• jmcs@discuss.tchncs.de
    link
    fedilink
    arrow-up
    0
    ·
    16 days ago

    Easy is relative. What are you trying to do? Replace a value in an yaml file? Then nano is easier. Trying to refactor a business critical perl/brainfuck polyglot script in production? Then you probably want to use vim (or emacs if you are one of those people)

    • notfromhere@lemmy.ml
      link
      fedilink
      arrow-up
      0
      ·
      15 days ago

      Honestly, roll back to previous release for production and use best IDE your developers are used to on their local machines, test the fix in a non production environment then release to prod. When is editing business critical scripts in production really needed?

      • jmcs@discuss.tchncs.de
        link
        fedilink
        arrow-up
        0
        ·
        15 days ago

        It was a joke to make the point that vim can be the easiest tool to use if you are trying to do a complex task.

      • voracitude@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        edit-2
        16 days ago

        I regularly fix my bashrc file with Notepad. I run it in Wine because I cbf to RealVNC from my Windows CE media server.

        (n.b: None of this is real, I wrote it to upset people, I’m sorry)

        • riodoro1@lemmy.world
          link
          fedilink
          arrow-up
          0
          ·
          edit-2
          16 days ago

          Well let me upset you.

          Ive been helping my coworker on a call and he was sharing his screen. I told him to edit a file (add a line) on a linux box we develop and he copied the file to his windows host with winscp, edited it in notepad and copied it back. I fantasize about killing him ever since.

          • Dave.@aussie.zone
            link
            fedilink
            arrow-up
            0
            ·
            16 days ago

            They need to learn how to use their tools better. Winscp does all that transparently for you if you press F4 on a file on a remote system. Or maybe they did and you just didn’t see it…

            It’s quite a handy function when you’re diving through endless layers of directories on a remote box looking for one config file amongst many.

  • ReCursing@lemmings.world
    link
    fedilink
    arrow-up
    0
    ·
    16 days ago

    Ugh, I swear vi and it’s derivatives are the absolute worse text editors going. There may have been reasons thirty or forty years ago, but now it’s just complexity and a weird ui for the sake of it

    • matthewmercury@reddthat.com
      link
      fedilink
      arrow-up
      0
      ·
      16 days ago

      I use VS Code on the desktop nowadays, but vi will always be my editor of choice in a terminal. Many of the reasons it was powerful and ubiquitous 30 years ago are still valid, so it’s still powerful and ubiquitous. And I’ve been using it for thirty years, so why would I switch to a training-wheels editor?

  • thingsiplay@beehaw.org
    link
    fedilink
    arrow-up
    0
    ·
    16 days ago

    The Terminator is not here to kill you, its here to protect you from Emacs (which can change its form to anything).

    • tetris11@lemmy.ml
      link
      fedilink
      arrow-up
      0
      ·
      edit-2
      16 days ago

      Cmon dude, what’s most likely to be Skynet?

      • Vim: Clearly evil, lightning fast. Relies on vimscript for any interactivity and can barely be used outside of the editor.

      • Emacs: the hippie brain child of some of the brightest minds at the MIT AI lab, funded by military contracts. Slow, but uses a near-universal language that can easily escape the bounds of the editor, (and often does (, and holy shit where did those parentheses come from. (Oh no, it’s becoming self-aware - fly you fools…!

      • thingsiplay@beehaw.org
        link
        fedilink
        arrow-up
        0
        ·
        16 days ago

        Vim: Clearly evil, lightning fast. Relies on vimscript for any interactivity and can barely be used outside of the editor.

        I don’t know why you want use Vimscript for anything outside of the editor. But if that your issue, then there is Neovim. It uses Lua instead Vimscript, but what is the benefit of using Lua outside of Vim? That changes nothing.

        • tetris11@lemmy.ml
          link
          fedilink
          arrow-up
          0
          ·
          edit-2
          16 days ago

          Lua outside of Vim has huge applications in embedded products. Dude I would kill for Lua. Do you know what we have? Common Lisp. Yeah, it’s great and fancy and all, but try adding that to your CV and applying for an embedded system job.

          • thingsiplay@beehaw.org
            link
            fedilink
            arrow-up
            0
            ·
            16 days ago

            My point is, then use Lua outside of Vim. What does this have anything to do with the language used in Vim? You can use Vimscript in Vim, and still use Lua outside of Vim. So what’s the problem? It’s not like Lua gets available to you outside of Vim, just because you switch to Neovim. What do I miss here?

            • tetris11@lemmy.ml
              link
              fedilink
              arrow-up
              0
              ·
              edit-2
              16 days ago

              (it was mostly a joke, but) the skills you acquire tinkering your Vim to your needs using vimscript can’t be used elsewhere, whereas Emacs has the (small) advantage that at least most of one’s elisp skills can be translated to common lisp quite easily (with the joke being that common lisp really isn’t that useful, hence my Lua jealousy rant).

        • cygnus@lemmy.ca
          link
          fedilink
          arrow-up
          0
          ·
          16 days ago

          It uses Lua instead Vimscript, but what is the benefit of using Lua outside of Vim?

          The only other (in fact, the first) place I’ve run into Lua is WoW plugins.

          • thingsiplay@beehaw.org
            link
            fedilink
            arrow-up
            0
            ·
            16 days ago

            But WoW plugins have nothing to do with Vim. That’s my point. You can use Lua in WoW, while using Vimscript in Vim.

  • Dasnap@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    16 days ago

    I started on Unix systems using Vim, so I find Nano to be the confusing editor. A Vim install is one of the first things I do on a new server.

  • RedWeasel@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    16 days ago

    Worst is when installing a new distro(usually in a vm ) and it defaults to nano and for some weird reason no vi of any sort is installed. I hated nano. Last time I intentionally used something like nano was the 90s with pine I think.

  • AnUnusualRelic@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    16 days ago

    The first time I found myself in nano was when testing a distro fifteenor twenty years ago. I had to edit some files and it was the only available editor. The damn thing was a horror to use. I still have no idea who it caters to. I haven’t had to use it since though.

    • SomeLemmyUser@discuss.tchncs.de
      link
      fedilink
      arrow-up
      0
      ·
      edit-2
      16 days ago

      Dunno what you used, but nano is literally a text editor that may be simple simple but it just works. Shortcuts are shown to the user, buttons work like you expect them to (arrow keys, ESC, shift, etc)

      With vim you open it and if you haven’t read 5pages of doc you won’t even be able to close it again. I see that its useful for power users, but for casuals who just want to edit a config once in a while nano is absolutely the way to go imho

      • AnUnusualRelic@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        edit-2
        16 days ago

        It’s not that simplle or user friendly when none of the usual shortcuts work. C-a did something completely unexpected.

        • SomeLemmyUser@discuss.tchncs.de
          link
          fedilink
          arrow-up
          0
          ·
          edit-2
          15 days ago

          Well its shown to you at the bottom of the screen what it does…

          And if you want Ctrl v,c,s etc. To work like in word etc you can always use nano --modernbindings

          • AnUnusualRelic@lemmy.world
            link
            fedilink
            arrow-up
            0
            ·
            15 days ago

            They’re in Linux now, it should show the shortcuts they’ll encounter everywhere. Not leftovers from another system.

  • m4m4m4m4@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    16 days ago

    The problem I had with nano is that, for the time being, it was supposed to be easy to use. With that in account I always get lost when saving a file and closing the thing because one’s used to doing something else with Ctrl+O and Ctrl+X.

    Whereas with Vim (and Neovim for a little while, and now with Vis) I knew it had a steep learning curve from the start so I always had it in mind. And all the funny stories about quitting vim.

    • tetris11@lemmy.ml
      link
      fedilink
      arrow-up
      0
      ·
      edit-2
      16 days ago

      they’ve changed those bindings now, Ctrl+S, Ctrl+X, Ctrl+V, and Ctrl+C all do what you think they do

      • m4m4m4m4@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        edit-2
        16 days ago

        Great, now the next time I use nano I surely will forget about this and get frustrated when trying to save a file with Ctrl+O

        • tetris11@lemmy.ml
          link
          fedilink
          arrow-up
          0
          ·
          16 days ago

          you still can, but I think Ubuntu and other prepacked distros will switch soon to the better bindings

          • socsa@piefed.social
            link
            fedilink
            English
            arrow-up
            0
            ·
            16 days ago

            Great so now I will mangle all my merge commits depending on which version the host is using.

        • tetris11@lemmy.ml
          link
          fedilink
          arrow-up
          0
          ·
          edit-2
          16 days ago
          • nano

            • Ctrl-Q search backwards
            • Ctrl-S and Ctrl-X is save file
            • Ctrl-V is scroll down
            • Ctrl-C is cancel or info
          • nano --modernbindings

            • Ctrl-Q quits
            • Ctrl-S is save file
            • Ctrl-X is cut
            • Ctrl-C is copy
            • Ctrl-V is paste
  • unknowing8343@discuss.tchncs.de
    link
    fedilink
    arrow-up
    0
    ·
    16 days ago

    In every post of this kind I am amazed at so many people using nano instead of micro which is SO MUCH BETTER while being the same thing at the same time.

    • sping@lemmy.sdf.org
      link
      fedilink
      English
      arrow-up
      0
      ·
      16 days ago

      And yet Emacs users don’t fight vim users. Emacs users decided vim’s interface was pretty cool and added it to Emacs. Somehow people still call it a war though.

      • kata1yst@sh.itjust.works
        link
        fedilink
        arrow-up
        0
        ·
        16 days ago

        Bruh 😂 the Emacs user community absolutely constantly shit on Vim users. When they added Vi(m) bindings they literally named it ‘evil mode’, and they constantly make fun of people who use it, and spacemacs, and the latest flavor of (neo)vi(m), and all the extensions necessary to make vim halfway useful as an ide, etc etc etc.

        • G0ne@lemmy.world
          link
          fedilink
          arrow-up
          0
          ·
          16 days ago

          Evil or the extensible vi layer is super popular and improves the one area that emacs was lacking i prefer the emacs keybinds but have never seen peeps chat shit about it

        • sping@lemmy.sdf.org
          link
          fedilink
          English
          arrow-up
          0
          ·
          edit-2
          16 days ago

          Which Emacs community? I’ve been following it for ages in a few places (Reddit is the most common) and I literally do not encounter any of that. Calling it evil was humor - as if people who went to all the bother making it would be trying to push people away…

          Using the evil package is very popular and often recommended, which means literally using it like vim, but with all the Emacs ability on top. I don’t know what on earth you’re talking about.

          • kata1yst@sh.itjust.works
            link
            fedilink
            arrow-up
            0
            ·
            16 days ago

            Oh to be clear, it’s all humor. At least mostly, I’m sure there are RMS level fanatics somewhere that truly believe some of the BS.

            This is something as old as time. I’ve seen it prolifically on Reddit (though not in the Emacs community, they generally discourage memes), various Linux forums, old Usenet, various programming forums… I’m not trying to be evasive, but it’s hard to provide examples that aren’t specifically cherry picked, which wouldn’t benefit the conversation much.

            There’s even a Wikipedia page dedicated to this: https://en.wikipedia.org/wiki/Editor_war

          • Opisek@lemmy.world
            link
            fedilink
            arrow-up
            0
            ·
            15 days ago

            How close to vim’s functionality is evil mode? I’ve been toying with the idea of learning Emacs but I rely on Vim’s langmap and that is rarely implemented in Vim emulations / bindings.

            • sping@lemmy.sdf.org
              link
              fedilink
              English
              arrow-up
              0
              ·
              edit-2
              15 days ago

              Although I came from vi (pre-vim and pre-evil) and still have the muscle memory, I don’t and haven’t used it myself.

              I hear it described as a “nearly complete” and “very comprehensive”. There is definitely a solid community of people using and enjoying it, but on the other hand there are always some reports of getting tired of having to work through, and sometimes extend, an additional interface layer, so in the long run being happier to just adopt the default bindings.

              I know there are a few areas where trying to follow common vim workflows doesn’t work as well. Historically the performance of line number display been weak in Emacs, though I believe it’s recently much improved. A lot of people seem to make heavy and constant use of it in vim but conversely for me (and I think it’s more common in Emacs) it’s only an occasional, transient need when some external log or error quotes a line number, so I have them only displayed when I hit the go-to-line binding.

              Overall, I think the most frustrating issues people have trying to adopt Emacs from vim are due to trying to impose their specific familiar vim workflows. The most obvious example is people concerned with startup time, but for more typical Emacs workflows it’s a non-issue. Users typically stay in Emacs rather than jumping in and out of it from a terminal (and if you really want that workflow, you run one instance as a daemon and pop up a new client to it instantly). My Emacs instance’s uptime usually matches my computer’s uptime.

              The draw of Emacs is not about it only being an editor so much as a comprehensive and programmable text environment. It is a lisp-based text-processing engine that can run numerous applications, the primary being an editor (the default, or evil, or others…) but also countless other applications like file managers, VC clients, subprocess management and many others. It 95% replaces the terminal for me, and many other tools. So it’s the environment through which you view and manipulate all things text that is very accessible to modify and extend to fit your needs. Hence the joke about it being an OS is pretty apt, though to believe it needs a good editor implies vim isn’t a good editor ;).

          • wise_pancake@lemmy.ca
            link
            fedilink
            arrow-up
            0
            ·
            edit-2
            15 days ago

            Same here.

            The biggest diss I have on emacs users, as a vim user, is that emacs is the only text editor where people routinely need to keep a book about it on their desk!

            I used to work with a bunch of emacs guys and they all had an emacs book or two on their desk or as a monitor stand. They usually also had one on awk and/or Perl to go with it.

            I’m sure they’d probably make fun of me for being unable to edit a file with anything but my specific vim config, which is not compatible with any other human’s vim config.

            (I would never seriously judge someone on their editor, but I will bust an emacs users chops and accept a good natured jab back)

    • skittlebrau@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      16 days ago

      Nano is more like fast food. It’s easy and convenient, but it makes you feel a little guilty and dirty afterwards.

      • ggppjj@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        15 days ago

        Nano is the tool that people use when they don’t have a need for TUI editors in general and therefore don’t want to have to memorize how people with teletypes decided things should have been done 75 years ago and who also don’t want to get dragged into endless pointless bickering arguments about which set of greybeards was objectively right about their sets of preferences.

        I’m glad people enjoy the editors they use and also I just wanna change a single fuckin line in a config file every once in a while without needing to consult a reference guide.

        • wise_pancake@lemmy.ca
          link
          fedilink
          arrow-up
          0
          ·
          15 days ago

          I don’t have much to say about nano, except the hotkey bindings are weird and unnatural.

          They make sense, but they feel wrong.