nvim-config
tree-sitter-jsdoc
nvim-config | tree-sitter-jsdoc | |
---|---|---|
9 | 2 | |
22 | 29 | |
- | - | |
8.6 | 6.4 | |
23 days ago | 7 days ago | |
Lua | JavaScript | |
GNU General Public License v3.0 only | MIT License |
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.
nvim-config
-
Need help setting working directory of my debugger for python in neovim
my config works fine without setting cwd. I have a helper module that gets the Python path from the currently active virtual environment.
-
how to avoid overlapping of gitsigns and lsp warning symbols in SignColumn?
Check my config for inspiration and the example screenshot above from my config.
-
Documentation Comment highlighting with TreeSitter
Not sure for Java (that’s Java right?), but for Python I inject rst in docstring comments. See here for my config.
-
What else can I do to speedup startup time?
How is anybody supposed to be able to help, given the information you provide? My setup with perhaps 60 plug-ins load in ~40ms (according to Lazy profile) on my M2 mac or ryzen 5600 workstation. You can take a look here.
-
How to fetch python installed path from lua?
My python helper, ftplugin and DAP executable
-
VenvSelect 0.2
Cool! I’ve written something similar in my config. But it only supports selecting conda environments. Typically I specify the venv and venvPath in pyrightconfig.json, so I use the code to show the current env in the status line and to supply the executable to dap and neotest.
-
Start conda envs after opening a file + conda envs telefoscope & Send to terminal (both for python)?
helpers/python.lua
-
After using Emacs (with evil) for a long time I switched to Neovim.
You should not add the ft = "latex" for VimTeX (https://github.com/isaksamsten/nvim-config/blob/main/lua/plugins/latex.lua)! VimTeX is already properly lazy by design (through use of ftplugin/ and autoload/). This is explained in a note just below the install instructions in the readme. :)
tree-sitter-jsdoc
-
Documentation Comment highlighting with TreeSitter
No perfect answer but hopefully that helps break things down a bit. Maybe a treesitter parser for doxygen comments could be created similar to this one for jsdoc.
-
Alternative Lua parser for nvim-treesitter. It closely follows the syntax of Lua in extended BNF (https://www.lua.org/manual/5.1/manual.html#8).
luadoc parser that is similar to what https://github.com/tree-sitter/tree-sitter-jsdoc is.
What are some alternatives?
statuscol.nvim - Status column plugin that provides a configurable 'statuscolumn' and click handlers.
nvim-treesitter-lua - Tree-sitter Lua parser integration for nvim-treesitter.
telescope-conda.nvim
tree-sitter-lua - Lua grammar for tree-sitter.
debugpy - An implementation of the Debug Adapter Protocol for Python
tree-sitter-lua - Neovim Tree Sitter Lua Grammar & Library
py_lsp.nvim - Lsp Plugin for working with Python virtual environments
nvim-treesitter - Nvim Treesitter configurations and abstraction layer
nvim-dap-python - An extension for nvim-dap, providing default configurations for python and methods to debug individual test methods or classes.
DoxyGen-Syntax - DoxyGen Highlighting on top of c/c++/java
NeoTerm.lua - You can attach a terminal-buffer for each buffer.
tree-sitter-comment - Tree-sitter grammar for comment tags like TODO, FIXME(user).