Let the flame war begin...

πŸ”₯πŸ”₯ Nano or Vi? πŸ”₯πŸ”₯

I've heard good stuff about NeoVim. Worth checking out coming from Vim8? I need to do some reading eventually.

I quite like it. One of the most useful features I've found is clipboard buffer syncing over SSH ootb. It's perfect for copying configs when you need to paste them somewhere. Switching from vim to neovim is also really easy:

mkdir ~/.config/nvim
cp ~/.vimrc ~/.config/nvim/init.vim

I made an alias for vim to nvim so I don't have to change habits lol


Oh clipboard syncing is really useful. And yeah, I'm the same way I would have to add an alias or always forget.

There are also some really cool plugins. The left buffer is a file manager, the bottom bar is a nice way of displaying some info, and on the right is a CSS file with hightlighted colour codes. I've also got a plugin that does IDE-like fuzzy autocompletions and I'm pretty sure it's only compatible with neovim. I don't know about the others though.


@kev @gxtony
That's not even in the same ballpark. Unusable in the terminal. πŸ™€

@kev based on my extremely limited experience, nano

but only cause I've never been arsed to learn Vim... Vim is probably better to learn overall though

@gaurdianaq I’m a nano guy for the exact same reason.

@kev like if i ever had to do some serious devwork in a command line environment and I didn't have the option of just transferring stuff via ssh or git I'd take the time to learn vim XD

@gaurdianaq yeah, but nano is just an apt install away. 😁

@kev does nano also offer options for plugins like vim does? Like for code highlighting/syntax stuff?

@gaurdianaq I don’t know to be honest. I’ve never actually looked into it.

@kev I remember being surprised to learn that Vim actually has quite an expansive plugin ecosystem that lets it act more like an IDE when setup correctly

I kind of went that direction for a while in Vim and never saw any slowdown or bloat but recently trimmed my config down to just the basics. The basics for me are syntax highlighting for the few languages I use often, NerdTree and airline, and autocomplete via completor.

If I find myself thinking I need an IDE for a project I'll use an IDE. Things like find all across the project, etc.

@kev @gaurdianaq
It does support syntax highlighting, but I don't know how to enable it :P. But either it's enabled on Debian by default, or a friend enabled it on all our servers when I wasn't looking.

@Wolf480pl @kev @gaurdianaq It's file extension based, and only appears when you're using a colour terminal.

@e8johan I know, I know, Nano is the outright winner! 🀣🀣🀣

@kev that is what I'm saying! Less is more! Nothing beats simplicity!

Nano is the first generation iPhone of editors - but *with* copy&paste!



don't ask me why cause just vi!!!


@mookie 🀣🀣🀣🀣🀣🀣

@mookie I didn’t even get a :wq 😭😭

@kev πŸ˜‚ πŸ˜‚ πŸ˜‚ πŸ˜‚ πŸ˜‚ πŸ˜‚ πŸ˜‚ πŸ˜‚ πŸ˜‚ πŸ˜‚ πŸ˜‚

I'll give ya a :wq! Just to force it.

@kev I use vi(m) just cause that's what I learned when I started using Linux. Just never felt the need to switch to anything else because I'm comfy in vi. Surprised you didn't throw in emacs to really fan the flames.

@kev I don't know when it happened, but these days nano is too complicated for me.

I fail hard on tasks like deleting a single line or saving a file that I opened with the wrong user.

That said, I started on vi due to a teacher, didn't like it, so when I wrote stuff myself using a CLI I went for nano back then.

As mentioned these days I use vim almost everywhere and feel like nano is too complicated to use. How time flies…

@sheogorath I think you’re the first person ever to say nano is too hard - I suppose that’s the beauty of all this choice we get.

@kev :D Sure, but can you tell me how to delete a whole line at one in nano? I really want to know that!

@ciaby @sheogorath @kev
you can delete more than one by pressing Ctrl+K mutliple times, and then paste them back somewhere else with Ctrl+U

If you need to move around bits of text that are in the middle of a line, just insert some temporary newlines, C-K, C-K, C-K, move cursor, C-U, then delete the temporary newlines.

@Wolf480pl @ciaby @kev

Great! This editor makes more sense now. Still, I guess I'll stay with good old vi/m. But this will definitely become useful when one of those Ubuntu machines greets me with nano as default editor!

@kev ok let me add my log into the fire

IntelliJ IDEA
@kev in seriousness tho i use nano when i need to

@kev Vi for me, or Vim, rather. However, I have yet to see a function that is different.

No flame war, though, I agree with @poetgrant that it's not a plug-and-play solution. In Vi's defense, however, it's EVERYWHERE on Linux. Bring up a random box and it'll be there.

Nano/Pico is difficult for me because Ctrl-strings.


>no ed master race.

@kev It would have to be Vi of course, I actually can't think of a system where nano is even installed that I use.

Editors are for newbies, I just use cat, grep, sed, awk, and echo with output redirection and pipes to manipulate files. Why introduce bloat?

@gentoorebel @kev Can you really call yourself a programmer if you don't do this? πŸ™ƒ

@kev It's two different types of programs imo: one that is easy to pick up and quick to make small edits with, the other has a much higher learning curve but can also be much more powerful. Personally I use nvim with plugins most of the time :)

I have always been partial to nano because it is the easiest of the β€˜in-terminal’ type text editors for beginners to learn.

@kev Vi, no question. I don't want to hear points about user-friendliness from people who save with Ctrl+O πŸ˜‚

Sign in to participate in the conversation

Fosstodon is a Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.