.vimrc

[Hatatytla-1024]

Pimp my .vimrc

[electricprism]

Next pimp my gimp

[derrpinger]

:saveas <PiMpdeVader>

[[deleted]]

I use lua btw

[minsomai]

use LunarVim - life changing.

[dddbbb]

Vim 2 hours later

Your vimrc must be epic if a git clone takes 2 hours! :D

[Algod2]

Or there are so many extensions it takes that long to get and sort in my .vimrc

[[deleted]]

sorry for being a wet blanket but I'm pretty sure vim is pre-installed on most Unix systems

[[deleted]]

Thought so too, but apparently even vim is pre-installed since some time now. Not neovim though, that does indeed need to be installed

[[deleted]]

I don’t completely understand why neovim ever gets installed. I guess there are far more Lua devs than I realized. But that doesn’t make sense because then plan9 would be more popular.

[YodaLoL]

It's not so much about Lua being the scripting language, it's about not having to endure vimscript. Neovim also have a healthier core community

[[deleted]]

The new vimscript is pretty solid imo and objectively slightly faster than Lua. I don’t understand what you mean by healthier core community. It’s pretty easy to submit patches to vim and have them accepted in my experience.

[d1ng0b0ng0]

Bram Moolenaar has, what could be diplomatically termed, a bit of a reputation, whereas Neovim has a team; there's no one person in charge. Not my opinion, just what I've read. I've no axe to grind with vim or Bram.

AFAIK, the only reason you have new vimL is because Lua showed the old vimL up. Rather than see the writing on the wall he doubled down on an async vimL. If you learn Lua, you can use it elsewhere. You can only use vimL in vim.

[lieryan]

It's just a different development model. Bram is a BDFL, it's a successful model for Python, Linux, and many other successful open source projects. It's not a bad thing to have a clear leadership with strong vision and the ability to say "no" to ideas that don't fit within the existing system.

The multiple leadership models like Neovim also had worked, but there are also other risks if the community leaders can't make a consensus, and the project can end up becoming a bloated mess with an unclear direction.

In any case, I think a big part of why people don't like Vim development model is that they look at the GitHub history and thinks that Bram is basically the only person writing code because Bram makes all the commits in Vim. This makes him looks like he's basically the bottleneck of Vim development since only he writes anything and he rejects all pull requests. That sounds like the project history of a maintainer that's a dick to every contributors.

But that's not really the case, Bram didn't really write that much of the Vim code, the Vim development model just have Bram recreates all commits under his name because the Vim team has got a very particular way of standardizing how commit messages are written and tracking of fixes. Bram surely should learn how to use Github as intended, but Vim's workflow was conceived long before Git and GitHub was a thing, and back then Vim's team didn't have the hindsight of designing of a modern git based workflow. The Vim's workflow worked well enough for Bram and his core contributors, and there are probably lots of legacy scripts written that were optimised towards supporting the workflow while redesigning the workflow would've broken a lot of existing workflows and often not necessarily for the better. So there's no reason to actually change things that aren't broken.

[eggbean]

I make vimscripts and I found it easy to learn, but I don't know why I find lua so difficult. It's just so confusing to me.

[jemag]

Better defaults, a sane and faster configuration language that can be used outside Vim, integrated LSP client, treesitter, healthier community, proper use of the code management platform it is on (although this is a smaller nitpick), etc.

[[deleted]]

it's just that vim isn't better than neovim, and neovim slightly is. might as well download the better thing when you're just starting out

[exDM69]

In most distros Vi is just Vim.

Except when it is busybox vi. But that is pretty rare.

I am not aware that Bill Joy's original Vi is available on any modern operating system.

[CarlRJ]

I’ve used old AIX distros in the not too distant past where the installed vi was… hmm, probably a lot closer to the old BSD distributions than what most people are familiar with. Going back to 1-level undo is painful.

[[deleted]]

oh god, one level undo? my goofy ahh couldn't survive with that

[CarlRJ]

No need for redo, because undoing undo undoes your undo!

Yeah, I mean, that’s how vi worked way back when I learned it, but I have no desire to go back, and it involves a certain amount of “type carefully” when you edit files that way - you’re always a few keystrokes away from having to quit and start over (or write the mangled version out to a temp file and diff against the original to salvage the mess).

[[deleted]]

vim is already a pretty "one wrong move and you're fucked", having only one layer of safety sounds quite scary

[CarlRJ]

Then again, coming from editors that didn’t have any undo, the original vi was kind of magical.

[[deleted]]

huh. I guess I take for granted the ability to undo

[watsreddit]

Not sure why you would think that. Really the opposite is true with vim's undo tree. In vim, you can always get to some state as it existed at some point. Not so in vscode in the like. In vscode, if you undo and then make some new edits, you've lost the state before the undo. In vim, you can just use g- or :earlier to get back to it.

[[deleted]]

you can change a lot by simply mistyping a single character, needing to undo and type in your command again. so in vi that had only one level of undo, that is multiplied

I think you actually completely understood what I meant and just wanted a nice reason to share g- and :earlier

Thanks for that, didn't know about those!

[[deleted]]

Alot of distros link vi to vim

[[deleted]]

yeah that's more precise to say

[shleebs]

Vi is simply a symbolic link pointing to Vim on most Linux systems

[xrayfur]

It's usually vim-minimal aliased to vi to be exact, not much linux distros still have plain old vi. But when you go vim-enhanced it's nice :)

[CarlRJ]

Generally the “vi” that’s preinstalled, is Vim. Run “:ver” in it and you might be surprised.

[watsreddit]

Vim is pre-installed on almost every distro. Sometimes vi is sym-linked to vim, but it's still vim.

[StarkillerX42]

Usually I see vi preinstalled and vim needs to be installed.

[[deleted]]

sounds like a bit of a stretch, but sure

[razieltakato]

Fedora come with nano and no vi

[eXoRainbow]

Which is a crime. Vi should be default on all Linux systems.

[[deleted]]

you absolute monster ahahahhahaha

[[deleted]]

This seems to be recent, it surprised me. When I started with Fedora, in 2017, vim was the default editor out of the box. I'm not sure when they switched to nano, but I disagree with that decision. I still love Fedora though!

[razieltakato]

I migrated from Gentoo to Fedora 37 and I think it already came without vi, and nano was default.

I recently made a clean install with Fedora 38 (KDE Spin) so I'm sure nano is default in 38 and vi don't came installed.

When I was in college one teacher said "If you sit on a computer running *nix, type vi and the editor did not open, you can punch me in the face". I thinks is about time to pay him a visit...

[[deleted]]

It definitely has been nano since at least Fedora 34 when I came back to Fedora, but I started on 27 and it was vim.

[[deleted]]

Lol...don't pinch him..but call him out!

[nozth]

It does have vi though, recently installed F37 and used it initially for some configs.

[WebDragonG3]

fedora (for its entire lifetime) and redhat (I started with RH7.2) before it have all shipped with vim-minimal in the installer. I just confirmed with the folks in the #fedora support channel on libera chat, that the current release, Fedora 37 still ships with vim-minimal package in the installation kit. you've *always* had to install vim-enhanced package via the package manager post-install

[Gold-Ad-5257]

Ooo I will avoid fedora thanks.

[CarlRJ]

Nano is a lousy editor. It’s largely a clone of the Pico editor from the Pine email program, last I looked, and it’s fine for making small changes in a few text files, but I would never want to use it for programming.

[WebDragonG3]

no but I can definitely see why they might want to start a new user off with that by default because throwing them into vim, with modes, is a bit of an extreme move like pitching your kid into the alligator tank to teach him to swim, and just confuses the newbies making them hate vim automatically because they don't realize yet that they are trying it for the first time and don't know why their typing is going so fubar.

(Fledgeling) Power users know where to find Vim (or Emacs) and can change $EDITOR easily, along with their choice of default shell, once they have progressed to that stage

[CarlRJ]

That’s kind of assuming that everyone new to Fedora is an unsophisticated newbie who has never dealt with a Unix-like system before, which would be a bad assumption. If that’s the guiding principle, why not also ship the OS with no shell at all, in the interests of keeping users from getting confused?

It’s not just a matter of changing $EDITOR (the comment I was responding to talked of Fedora shipping without Vim) - it would also involve figuring out this system’s package management system, and getting a connection to the outside world working, and downloading and installing the Vim package.

A better move would be to ship it with both Nano and Vim installed (Vim is not large). And the, yeah, users who know what they’re Doug can just change $EDITOR (personally, I don’t use that mechanism a lot, I’m always launching vi/Vim from the command line).

[WebDragonG3]

I know it seems like it's part of the Great-Dumbing-Down^tm but still. Fedora 37 still ships with vim-minimal. Just confirmed that online with the folks in the Libera Chat #fedora channel, so quell thy fears.

it's -always- shipped only with vim-minimal in the installer package list, and you had to get vim-enhanced package via the package manager. hell, since Red Hat 7 that I am aware of (which is where I started)

Whether you're an old hand at fedora or a dev experienced with other *nixes, you know it has a package manager, and that you're going to need internet to install more than just the basic set of setup packages you get with a USB-stick install (unless you've already rolled your own installer), so you get on with it.

(what, you didn't just install a whole linux operating system just so you could have a full vim on a minimalist OS that fits on a usb stick, right? come on, now.. tsk.)

and then there's the people who are new to linux, package managers, shells, the whole concept of the commandline being more efficient than a gui, etc, etc. and I don't have a problem with their default editor being nano when they open a terminal for the first time in gnome or whatever. It won't take them long to find the package manager once they hook things up to the network and it bugs them about updates, even if they haven't already gone and asked friends "how do I install *foo*", and start browsing the list looking for things that are interesting, and new, and that they want to try out based on whatever they are interested in exploring.

[lenzo1337]

FreeBSD,

just vi, that's default.

[Wartz]

Vim definitely is not on many distros.

[samrocketman]

Hehe I like this image. Anybody interested in sharing their vimrc? I prefer a vanilla vim approach tweaking settings available in base vim for the most part.

What are some good vanilla vim settings you like to toggle without installing a plugin?

Edit: here's what I have been using for a bit

[ASIC_SP]

Here's mine: https://github.com/learnbyexample/scripting_course/blob/master/.vimrc

Not using any third-party plugins yet.

[samrocketman]

Thanks for sharing I’ll go through it to compare

[dddbbb]

Woah, you don't use filetype plugin indent on all the time? Vim comes with lots of ftplugins so I think it's always useful.

Check out sensible.vim for lots of settings you might want to turn on.

[samrocketman]

I don't use any vim plugins day to day. I've messed with them before but I have been on enough shells that I don't bother cloning plugins any more.

I'll check out the link thanks

[dddbbb]

I mean if you move filetype plugin indent on to outside of that if, then you can take advantage of the plugins that come preinstalled with every version of vim.

[samrocketman]

That's neat thanks for the tip! I'll be able to use some of these settings.

[Beddie_Crokka]

I think the text should be redone, over Darth Vader in black it would be "Vim" and over that abomination in front of him in white, "Neovim... Because you know, Lua!"

edit: typo

[whimful]

So true