Which text editor do you use?

  • Allero@lemmy.today
    link
    fedilink
    arrow-up
    22
    arrow-down
    1
    ·
    2 days ago

    First choice: use a normal damn GUI text editor

    Second choice: Nano. It’s simple and comprehensible, and a best CLI choice for newbies. You can then turn to vim, emacs, or whatever, but don’t make your life harder from the get-go

    People suggesting to start with Vim are probably the same ones pushing for Arch as a first distro. C’mon.

    • zerofk@lemmy.zip
      link
      fedilink
      arrow-up
      13
      arrow-down
      2
      ·
      2 days ago

      That’s how you breed scrubs who can’t M-x-butterfly. I say give them a distro that boots into vi and starts a background process that block internet access around them. If they manage to quit vi and kill the daemon, they’re ready for Linux.

    • da_cow (she/her)@feddit.org
      link
      fedilink
      arrow-up
      8
      ·
      2 days ago

      use a normal damn GUI text editor

      The right choice as long as you don’t want to edit code/config files. Trust me, writing code inside libre office is not fun.

      • cockmushroom@reddthat.com
        link
        fedilink
        arrow-up
        8
        ·
        1 day ago

        Libre office isn’t a text editor it’s a document processor; more like a gui for something like TeX, or realisticially html, than a program for reading/editing plain text.

      • Allero@lemmy.today
        link
        fedilink
        arrow-up
        7
        ·
        1 day ago

        Kate is a basic GUI text editor that can highlight syntax, suggest options and do other things useful for code and configs. Comes with KDE (which is a common newbie recommendation) and is available as Flatpak everywhere else.

        But sure, there are instances where you should use CLI text editors. If you need to edit text files as root, this is generally the best option. Also, it’s the only option for headless setups and SSH. For that, nano will do.