unix-as-ide VS lazy.nvim

> I've never understood why people and to extend vim to try to make it half of an IDE.

Because vim ships with on any *nix machine and provides a consistent experience no matter where you use it.

Vim is the DE part and people add plugins or whatever to enrich the text editing experience with LSPs or other language aware plugins, and the I in IDE is in the form of the integration with the tooling already available.

This[0] might shed some better light on the "why"

[0] https://blog.sanctum.geek.nz/series/unix-as-ide/

Check out “UNIX as an IDE”. First Google hit; https://blog.sanctum.geek.nz/series/unix-as-ide/ There are some great talks on YouTube but can’t be bothered to search :)

I use the CLI as my IDE. For me, that's FreeBSD or OpenBSD most of the time with a little bit of Linux (and as little Windows as possible). I usually wrap it all in a tmux session, but with vim/neovim offering :terminal functionality these days, I could see an alternate universe where that got flipped/inverted.

See Unix as IDE for an example.

I choose vim/neovim because I need a "just" code editor, and also it can be easily leverage my tools capabilities on UNIX way, and you can read more on this article Unix as an IDE, but the all-in-solutions, like an IDE, is not the right tool for code editing, it came with a lot of features and defaults that you in most cases I don't need it, or I have to learn how to use them according to that IDE.

Your teacher probably subscribes to the idea of Unix as an IDE, and I do too! It's important IMO to avoid holy wars, but there are some spectacular tools built into your Unix computer if you take the time to get to know them.

Vim is first and foremost a text-editor. In the Unix philosophy other tools should fill the places of the functionality a fully-fledged IDE gives you. You can add plugins and heavily craft your .vimrc to make it a lot like an IDE. But that's not really the "unix way" so to speak. I'm not necessarily some sort of coding elitist. I'll settle for other tools when I have to. I've also spent more hours than I care to admit making VIM more or less an IDE. But there is a sort of simplicity in being able to develop remotely in a test environment using vim and few other CLI tools. I recommend checking out Unix as and IDE for an intro to what I'm talking about.

Yes, this helped me https://blog.sanctum.geek.nz/series/unix-as-ide/

First, I installed NeoSolarized.nvim via lazy.nvim, so the code would be simple like the following one.

In my case, I have switched to Lazy.nvim for all of my Neovim plugin needs ( Thanks again Folke! ), so it would be great if you were at least minimally familiar with how Lazy works as well.

If you've read old tutorials about Neovim configuration you've find the way they create keymaps is a little bit different from what people do now. And if you check other people's configuration sometimes you'll find they create their keymaps using lazy.nvim. This is causing confusion among Neovim users.

The basic plugins will be downloaded on the first run using Lazy, a package manager for Neovim that loads only the necessary plugins as you use them. Once it's done you should be looking at a full-fledged IDE.

it looks more like something is wrong with your neovim install rather than your config. based on this lazy.nvim issue you may have an updated neovim binary but your neovim runtime files are not up to date. try completely reinstalling neovim.

It is possible to manage plugins yourself, but I would recommend a plugin manager such as Lazy (https://github.com/folke/lazy.nvim). There are many more plugins that most would argue are virtually essential, but these should at least be able to get you some autocompletion and highlighting without too much messing about. Be sure to read the install instructions for each of these plugins!

whenever i add this: ``` -- bootstrap lazy.nvim local lazypath = vim.fn.stdpath("data") .. "/lazy/lazy.nvim" if not vim.loop.fs_stat(lazypath) then vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", "--branch=stable", -- latest stable release lazypath, }) end vim.opt.rtp:prepend(lazypath)

Easily updatable. Versions are stored in manifests and can be easily updated with a single command. neovim's lazy-lock.json however is managed separately by lazy.

require("keymaps") local lazypath = vim.fn.stdpath("data") .. "/lazy/lazy.nvim" if not vim.loop.fs_stat(lazypath) then vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", "--branch=stable", -- latest stable release lazypath, }) end vim.opt.rtp:prepend(lazypath) require("lazy").setup({ "folke/tokyonight.nvim", {"nvim-treesitter/nvim-treesitter", build = ":TSUpdate"}, { 'nvim-telescope/telescope.nvim', tag = '0.1.4', dependencies = { 'nvim-lua/plenary.nvim' } } })