Changing from a distro that defaults to nano to another that defaults to vim… What to do other than installing nano and changing visudo?

  • 00xide@lemmy.ml
    link
    fedilink
    arrow-up
    2
    ·
    1 day ago

    neovim through nvf on NixOS. I’m not even a power user, I just had a shit mouse in college and didn’t want to use it and now I’m hundreds of lines of Lua too deep to go back. This is my life now.

  • Ithral@lemmy.blahaj.zone
    link
    fedilink
    arrow-up
    3
    ·
    2 days ago

    Micro is pretty nice, has limited mouse support in the TUI line numbers highlighting. That or Neovim customized

  • CodeAssembler@lemmy.ml
    link
    fedilink
    English
    arrow-up
    2
    ·
    2 days ago

    Mostly Neovim and Nano. Tried out ed in the UNIX4 tape that got recovered, was strange but fun to see where sed, grep and other commands got their name from.

    GUI is still good old Sublime Text, but I almost completely switched to terminal based editors, I guess because of the nice work flow.

  • spacetff@lemmy.ml
    link
    fedilink
    English
    arrow-up
    4
    ·
    2 days ago

    nano, vi, geany, kate…

    I prefer nano - simple to use & always available. I manage remote systems often from my mobile using termius: config file editing, writing simple scripts for some analysis/automation tasks and recording task notes and status. Using a tablet I might use vi but generally prefer nano.

  • abra_k@lemmy.blahaj.zone
    link
    fedilink
    arrow-up
    4
    ·
    2 days ago

    Helix: Barely needs a config. But they are also pretty close to done with a plug-in system for the stuff that isn’t implemented by default :D

  • Dessalines@lemmy.ml
    link
    fedilink
    arrow-up
    2
    ·
    2 days ago

    Was staunchly team vim for 15 years, but now I’m on helix. As another user stated below, its like if vim were re-designed today, and without needing any addons to be a code-aware editor.

  • Nibodhika@lemmy.world
    link
    fedilink
    arrow-up
    4
    ·
    2 days ago

    When I first started using Linux I used Kate, I know, I know, not command line, but I didn’t needed a command line editor for my own computer. Eventually I started using nano for quick edits and that became my default CLI editor for a while. I don’t remember what I used as an IDE back then, but maybe it was Eclipse, although I think it was mostly just Kate.

    Eventually I decided to learn either VI or Emacs, and a friend who used Emacs pushed me to that side. I ended up switching everything to emacs, CLI, IDE, I even learnt org-mode and had tables and presentations in it.

    Eventually my pinky started to hurt too much, so I switched to Pycharm for python, and kept emacs for C++, text edits and org-mode. I ended up slowly switching emacs everywhere and reverted to nano.

    Some years back I decided to properly learn vim. I have been using nvim for a few years, and while it’s not the everything tool that emacs was for me, it’s still pretty darn useful. I also haven’t become a movement ninja and oftentimes I go wwwwww to get where I want to be. But still, there are some very nice shortcuts that I use a lot like Change Inside/Around or Delete X lines. Macros are cool, and sometimes feel magical, but other times they don’t work like I expected and I can’t figure out why. I don’t see myself changing to something else, the ubiquity of vim shortcuts in other programs makes it very convenient when I have to use something else.

  • Levi@lemmy.ca
    link
    fedilink
    English
    arrow-up
    70
    arrow-down
    1
    ·
    4 days ago

    Team Vim. Because I learned the vim basics once 20 years ago and never bothered to learn after that. :D

      • azimir@lemmy.ml
        link
        fedilink
        arrow-up
        7
        ·
        4 days ago

        That’s what I was taught at my first tech internship. It’s all they had on the UNIX system running the webserver in 1998.

        I did write some web pages the pulled live data from the backend. I had the pleasure of writing them in C. I got the data binding to some kind of CORBA system using extern variables that were bound at compile time. All of the html (no js or css yet) was hand built and generated from the C code.

        vi was the only editor on the system and there was no way to use arrow keys (the UNIX system didn’t have them on the keyboard at all).

        I also had the displeasure of building a backup system on a floppy where I had to write a bat script that could manually load a token ring driver, bind a SMB share, load Ghost backup software and backup the local hard drive at under 2mb (yay coax thicknet). The tool used to query and write through the hostname for the backup? Copycon. Fucking copycon in DOS. That showed me how a terrible (but working) tool could be to work with.

        Unless an editor can do reasonable vim emulation, I can’t take it seriously. You’re welcome to use it, but I won’t be able to get anything done in it quickly. The vi keys are too ground into my reflexes.

    • HeHoXa@lemmy.zip
      link
      fedilink
      arrow-up
      6
      ·
      4 days ago

      Vim sorely underrated. Great tools/hotkeys. Felt like a master pianist clacking away while the terminal went berserk until suddenly the 2 hour job was done in 20 minutes.

  • IrritableOcelot@beehaw.org
    link
    fedilink
    arrow-up
    4
    ·
    2 days ago

    My first experience with *nix was a professor leading me into a server room though two biometric locks and setting up the config files for a compute cluster faster than I would have been able to open the files.

    He was using Vim, and though it took me a while to learn, the sheer speed with which he was able to get us out of that unbelievably noisy server room sold me for life.

    Well, I use vim for text edits and nvim+extensions for an IDE. As close to a vim purist as is reasonable. But frankly, it’s the first one you learn to use well.