vim-blueplanet
nvim-dap
vim-blueplanet | nvim-dap | |
---|---|---|
2 | 138 | |
10 | 4,892 | |
- | - | |
9.2 | 7.7 | |
about 2 months ago | 5 days ago | |
Lua | Lua | |
- | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
vim-blueplanet
-
FAVOURITE PLUGINS
To my knowledge vim-test has no out-of-the-box configuration for TypeScript. I forgot why. Anyway here is my configuration that adds mocha and jest as testers for TypeScript. Though it is mostly based on the existing JavaScript support of vim-test it adds some extra support for Vue testing and project local binaries. Finally ensure you enabled these testers in the vim-test configuration (g:test#custom_runners).
-
Do you use a single init.lua/.vim file or an organized directory structure? Just curious :)
You could take a look here at my configuration. Not sure if that is helpful. You should first read up native packages as it has been linked above. I don't explain the little sneaks and features here. But in its core I put file and directory structure above everything else. I barely import anything manually but fully rely on automated mechanisms. I use lazy loading heavily. I use a mix of .vim and .lua files depending on its content and which language is easier (e.g. mappings are simpler in VimL. In result I have hundreds of files in my configuration. My everything follows a structure. With tools like fzf or telescope it is too easy to open the file you search for. It's basically no overhead. It would be more work to find what I search for if I would have less files. Finally this keeps everything incredibly independent. I can add, change and especially remove thing very easily as most things are very separated and independent. I want to remove a plugin, all its config, mappings, highlights, signs, ... I just remove one directory. Nothing more and nothing less. Clean cut. If I want a plugin and everything around it (copy-paste from above) to be lazy loaded it just works out-of-the-box. It's very simple and elegant. In my opinion. Though you can easily dislike it if you don't agree that strong with the approach it's fundamental arguments.
nvim-dap
-
I can't stand using VSCode so I wrote my own (it wasn't easy)
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.
-
Can you get better dapui varibles?
https://github.com/mfussenegger/nvim-dap/issues/1062 https://github.com/mfussenegger/nvim-dap/issues/737
-
How to start using Neovim for c++ development and debugging
Also, you can set up debugger integration with https://github.com/mfussenegger/nvim-dap .
- Build and run in one task using asynctasks.vim
-
How can I debug Python code in neovim!
You could use nvim-dap with nvim-dap-python.
-
How to debug python code in neovim
I'd suggest starting with a Neovim distro that makes things work for you and as you get familiar you can transition to a more custom configuration as you see fit. If you want to do it by yourself then the most popular plugin for debugging in Neovim is nvim-dap and there is also an extension for Python to give you a more ready to go config instead of doing it yourself. You should read the docs of those 2 to see how you should customize accordingly your configuration.
-
How to configure vim like an IDE
(neovim only) nvim-dap
-
How to display variable values inline?
https://github.com/mfussenegger/nvim-dap + https://github.com/theHamsta/nvim-dap-virtual-text should be able to do it, I think?
- New Nightmare, the Hammerhead Worm
-
Q: Setting up typescript debugger for neovim?
If you want to debug types in TypeScript, you could use marilari88/twoslash-queries.nvim. If you would like to debug TypeScript/JavaScript code, then you need mfussenegger/nvim-dap, you could read this article: Debugging using DAP to understand how to set up it.
What are some alternatives?
material.nvim - :trident: Material colorscheme for NeoVim written in Lua with built-in support for native LSP, TreeSitter and many more plugins
vimspector - vimspector - A multi-language debugging system for Vim
nvim - Simple and ready configuration for neovim(nvim) with LSP. Inited with rust and go support
LunarVim - 🌙 LunarVim is an IDE layer for Neovim. Completely free and community driven.
octo.nvim - Edit and review GitHub issues and pull requests from the comfort of your favorite editor
nvim-gdb - Neovim thin wrapper for GDB, LLDB, PDB/PDB++ and BashDB
vim-gitgutter - A Vim plugin which shows git diff markers in the sign column and stages/previews/undoes hunks and partial hunks.
nvim-dap-python - An extension for nvim-dap, providing default configurations for python and methods to debug individual test methods or classes.
CodeLLDB - A native debugger extension for VSCode based on LLDB
vscode-cpptools - Official repository for the Microsoft C/C++ extension for VS Code.
my-lunarvim-config - My config for LunarVim
vscode-js-debug - A DAP-compatible JavaScript debugger. Used in VS Code, VS, + more