I watched oppenheimer in emacs, u watched it in imax, we are not the same

    • Xylight (Photon dev)@lemmy.xylight.dev
      link
      fedilink
      English
      arrow-up
      50
      ·
      1 year ago

      An extremely extensible text editor, there’s jokes that it can do literally anything, you can play music, watch video, etc.

      It’s often at war with the cult of vi and the church of emacs.

        • drcobaltjedi@programming.dev
          link
          fedilink
          arrow-up
          3
          arrow-down
          1
          ·
          1 year ago

          I don’t do a lot of text editing in terminal, but I used to have to at my last job and I always reached for nano and gave instructions fot nano since it’s just pick up and use.

          • heimchen@discuss.tchncs.de
            link
            fedilink
            arrow-up
            7
            arrow-down
            2
            ·
            1 year ago

            Nano just feels sluggish as soon as you know vim keybindings. Emacs is a bit overkill for some quck edits, but nano is just to basic

            • cybersandwich@lemmy.world
              link
              fedilink
              arrow-up
              5
              ·
              1 year ago

              Nano is a fantastic default editor for gui-focused distros. If you aren’t a command line wizard, nano is a better default because it’s a lot more straightforward.

              That said, nano is incredibly limited and if you have any experience with vi/vim/nvim, it’s the best solution full stop. It’s so much faster and more powerful but hot damn is it unintuitive for noobs.

              • SubArcticTundra@lemmy.ml
                link
                fedilink
                arrow-up
                4
                ·
                edit-2
                1 year ago

                As a nanoite who couldn’t be bothered to learn editor commands, I switched to turbo, which is essentially a linux port of the DOS text editor

              • AnarchistArtificer@slrpnk.net
                link
                fedilink
                arrow-up
                2
                ·
                1 year ago

                I was using vim for the first time the other day and I was running through the built in vimtutor. I got a call from a friend and they asked what I was up to, and I said I was doing a tutorial for a text editor. At that moment, I felt simultaneously very silly and very smart.

            • AnonStoleMyPants@sopuli.xyz
              link
              fedilink
              arrow-up
              4
              ·
              1 year ago

              By “as soon as you know” you mean “as soon as you have put those bindings to muscle memory”. Knowing them isn’t really enough.

              • russjr08@outpost.zeuslink.net
                link
                fedilink
                English
                arrow-up
                1
                ·
                1 year ago

                Well yeah, I’d say the same concept applies to using anything tech related these days. It’d be like if you “knew” where all of the keys on a keyboard layout that you don’t normally use are located - you’d still need muscle memory to actually use it efficiently.

            • drcobaltjedi@programming.dev
              link
              fedilink
              arrow-up
              2
              ·
              1 year ago

              Yeah, again, I don’t do much terminal text editing. I have an IDE. If I’m trying to help someone across the country 1000 miles away fix something on the machine I develop for, I’m going to give them instructions on something that will be incredibly easy to use. I don’t want to have to explain why the arrow keys aren’t working and why they have to use jkl; to navigate or explain how enter edit mode or how so save and exit. Keep it simple stupid.

      • barsoap@lemm.ee
        link
        fedilink
        arrow-up
        5
        ·
        1 year ago

        You should really convert to helixism, the latest messianic update to the cult of vi.

          • barsoap@lemm.ee
            link
            fedilink
            arrow-up
            5
            ·
            1 year ago

            I mean it does support LSP, natively, I found that ultimately that’s all the plugins I really need. It working out of the box and not requiring megabytes of configuration files is one of its great strengths.

            If all you need is some customisation it’s perfectly possible to write custom commands that execute sequences of commands. Including calling out to the shell and piping to and from external programs. Strictly static sequences though unlike the abomination that is vimscript they’re not making keybindings a scripting language…

        • pimeys@lemmy.nauk.io
          link
          fedilink
          arrow-up
          3
          ·
          edit-2
          1 year ago

          I’m a vim and emacs user for some decades already. I had this urge one day to try and work with helix. It kind of misses some things such as file manager or editorconfig support. Nine months later I’m still using helix. It still misses these things, but I really started to like how I don’t need any plugins to work with it and I need about five lines of configuration to have a usable editor. Probably going to continue using it.

          And it is written in Rust, which is my main language and I can just jump in to the editor source and fix things if needed.

          I miss magit and org from emacs a lot though. Every time I need to write an article, I do it in emacs.

          • barsoap@lemm.ee
            link
            fedilink
            arrow-up
            2
            ·
            edit-2
            1 year ago

            Indeed. Make sure to start it with hx --tutor the first time around so you know how to quit :)

            And no matter what you do when giving it a try do it in a time and place where you can go at least a week without vi as the command grammar is close yet different enough to completely confuse your muscle memory, you don’t want to mix them up (helix uses a strict selection-action command set so you get ‘wd’ instead of ‘dw’ and stuff).

    • aport@programming.dev
      link
      fedilink
      arrow-up
      6
      ·
      1 year ago

      A self-documenting, extensible lisp computing environment that uses text buffers as its main data format.

  • victron@programming.dev
    link
    fedilink
    English
    arrow-up
    6
    ·
    1 year ago

    Late 30s dev here: I’ve never cared to learn emacs or vim, tried when younger, but left it. Am I a fraud?

    • edriseur@jlai.lu
      link
      fedilink
      arrow-up
      5
      arrow-down
      1
      ·
      1 year ago

      I used to be a vim fan but now I only use it for modifying files over SSH. Other than that I code with an IDE, you can’t beat all the plugins and linters with a in-terminal editor. A colleague still codes in emacs and its code is dirty af.

      • siriusmart@lemmy.worldOP
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        I mean, I use a plugin manager for Neovim myself, and you can pretty much configure it to however you like.

        Someone even make an inline markdown preview for the editor using sixels (in terminal image display).

        but still I prefer the markdown preview plugin as it previews the file using a browser is format rly similar to github’s styles