dotfiles VS vimspector

You put your snippets in a lua file, like here (with syntax according to the luasnip documentation) and invoke such file somewhere in your configuration so that it's required (i. e. "loaded").

Without knowing your precise folder structure and where you are requiring what is a little hard to understand. However, I do something similar but I have a functions file in my lua folder (without any nested subfolder) and I just require all the .lua stuff in my init.lua here.

Some examples here, but as other users suggested it's vim.filetype.add().

You can find my snippets here: to be honest they are rather simple, so creating such doesn't take me too long. In general I would say either style is fine (or equally ugly :p).

Whilst at the moment I do not have time to go through your config, this is my noice config and my lsp. You can copy&paste, I have borders set and normal highlight window. It works, so just copy it and then work back till you add yours.

If it can be of help this is my noice configuration and lsp setup. It is working fine for me and I tested updating everything right now.

See examples here.

Here - it is just a config file with a few functions: use it as inspiration! The code is probably not optimised yet (I just got it working and I wanted to share, do let me know if you can make it better): mappings to operate

I use navi and I am very satisfied: it's very easy to create your own cheatsheets, see for instance what I do here.

It is macOS with iTerm2 and zsh as shell. The DE is the standard one that comes pre-installed, I didn't make changes; you can find my configurations here

There are DAP extensions for both Vim (e.g. https://github.com/puremourning/vimspector) and NeoVim (https://github.com/mfussenegger/nvim-dap). I can't speak as to the experience in detail (I think I briefly played with nvim-dap a year or two ago), but I suspect that for most it will be good enough.

I struggle a bit to put what i want into words but i still try my best.So i got some plugins likehttps://github.com/sindrets/diffview.nvimhttps://github.com/harrisoncramer/gitlab.nvimhttps://github.com/puremourning/vimspectorand so on (but those are the one which i need that "feature" the most).

The actual title is "Vimspector - A multi-language debugging plugin for Vim".

It is a UI around DAP: https://github.com/puremourning/vimspector#what-vimspector-i...

vimspector

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.

You could try vimspector. It's main target is vim and not neovim.

https://github.com/puremourning/vimspector/

I use vim for C++ coding, however it is a bit difficult to set up to make it productive. I use YouCompleteMe [0] for autocompletion, Vimspector [1] with the C++ plugin for debugging, ALE [2] for linting, along with a few other general plugins (such as NerdTREE for file view).

[0] https://github.com/ycm-core/YouCompleteMe

[1] https://github.com/puremourning/vimspector

[2] https://github.com/dense-analysis/ale

For debugging normally I'd throw a breakpoint() and then have it launch pdb in a terminal from within nvim, but vimspector also exists if you'd rather.