unix-as-ide VS vim-fugitive

> 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/

the only reason I do some git stuff in vim and not _always_ in the shell, is because tpope is very thoughtful and fugitive.vim provides nice ways to deal with hunks or hunk partials (visually selecting a range within a hunk, for i.e.)

https://github.com/tpope/vim-fugitive/blob/master/doc/fugiti...

I agree, navigating blame history is incredibly useful, if only to save you from asking the wrong person about a particular change.

Vim's Fugitive[1] can do this and also in Textmate to. So I would hope that most editor git plugins can.

1. https://github.com/tpope/vim-fugitive

Git: vim-fugitive and gitsigns.nvim

You'll want to invest the time in learning Magit, which will change your life once you get the hang of it (and I was a heavy user of Fugitive in Vim previously!), and it's unlikely you'll find a better integration with GDB anywhere else on the planet than with Emacs, though I can't say that empirically. You just need to take the plunge and start learning it, then cut over and take the hit in productivity one day when you're feeling adventurous. You'll ultimately become far more powerful than you've ever been. Especially if you delve into elisp over time. I use Spacemacs, which is bloated and has bugs, but it has so many features that I haven't undertaken the massive endeavor to replace it from scratch yet.

For an option that works on Vim, if you already use tpope's vim-fugitive, there's vim-rhubarb (for GitHub) and fugitive-gitlab.vim (for GitLab).

I replace vim-fugitive with :! git

The only thing I truly miss from Emacs is [Magit](https://magit.vc/) since I still consider it the best git wrapper available. It is just too good. Unfortunately [Neogit](https://github.com/TimUntersberger/neogit) is not quite there yet although I hope it makes it at some point. I didn't like [Fugitive]https://github.com/tpope/vim-fugitive), but I ended up finding a good enough workaround by using [Lazygit](https://github.com/jesseduffield/lazygit) through [Toggleterm](https://github.com/akinsho/toggleterm.nvim).

I do think VSCode is a great tool and I recommend it frequently to people, but I still want to set the record straight here. Yes, vim is obviously limited in the sense that as a CLI app it doesn't draw it's own PDF or HTML windows, that's fair. But it can remote control your favorite PDF viewer or browser for roughly the same functionality. I'm currently writing my thesis using vimtex and it's quite smooth. And all the other stuff you mention is implemented quite competently by various plugins like vim-fugitive, coc.nvim, vimspector and copilot.vim.

Edit: je viens de trouver [https://github.com/tpope/vim-fugitive de Val