vim-prettier VS vim-fugitive

and prettier https://github.com/prettier/vim-prettier

You can still use vimscript plugins in the same way in neovim as you do in vim. In particular there's a specific plugin: https://github.com/prettier/vim-prettier

Prettier (https://github.com/prettier/vim-prettier) seems to work fine on html and javascript files. But when I run :PrettierCli on a lua file it says No parser and no file path given, couldn't infer a parser. I have treesitter installed. I used treesitter's ":TSInstall: lua" and :checkhealth shows a lua parser installed. Not sure what I'm missing or what to do to troubleshoot from here,

Have you looked through the configs for vim-prettier? Maybe exec_cmd_async

auto-formatting - prettier

I have been using vim for much much time now. Everything is going well but every time I want to format my code I got stuck. I have tried many plugins like vim-autoformat which is not formatting correctly (not the major filetypes like JSX, TSX), vim-prettier which is very slow and I have to wait some seconds to get the file formatted correctly, coc-prettier this was my favorite but I shifted to LSP so no usage of this plugin now.

Personally I like to use plugins (prettier/vim-prettier / fatih/vim-go) for added simplicity and less manual configuring (less filetype based configuring etc.).

Vale considerar também o Prettier:

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