go.nvim VS vim-fugitive

Also, I recently started using the nightly version of Neovim and I noticed that my queries were not working, so between version 0.9.4 and 0.10.0 of Neovim there are breaking changes in terms of treesitter queries, I suggest you go to this file in the ray-x/go.nvim repository so you can see the queries for both Neovim 0.9.4 and 0.10.0 versions.

To clarify, I want https://github.com/ray-x/go.nvim ability to invoke golines when formatting. Now I want to replace the default format on save with :GoFmt for Go files. (Already verified that invoking the command manually does what I need.)

You can try https://github.com/ray-x/go.nvim or at least use it's code to implement sql embed.

I have had this problem because of too many dap extensions, go.nvim and other golang plugins. These plugins have many auto keymaps, i delete some of them and fix this problem,but i dont remember the detail what i delete. Hope i can help you

I've not used it but apparently this has been recommended before for Go dev with Neovim: https://github.com/ray-x/go.nvim

This is my neovim setup with ray-x/go.nvim

There are a handful of really good go plugins that take care of this for you, such as https://github.com/ray-x/go.nvim or https://github.com/fatih/vim-go

point noted, thx. I have this link : https://github.com/ray-x/go.nvim

If you are using ray-x/go.nvim, then try :GoCodeLenAct while your cursor is on the same row as the virtual text.

I'm using lazyvim. everything is working as expected for Go Dev environment. I'm using this plugin for the configuration ray-x/go.nvim. My problem is that the selection movements work, like af, if... but for movements like '[m', it's not working, I just get the default behavior of moving to the next '[' and not the start of the method.

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