startuptime.vim
nvim-jdtls
startuptime.vim | nvim-jdtls | |
---|---|---|
5 | 75 | |
283 | 934 | |
- | - | |
0.0 | 7.0 | |
over 1 year ago | 2 months ago | |
Vim Script | Lua | |
MIT License | 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.
startuptime.vim
-
How can I profile neovim plugins for a specific file?
You could use https://github.com/tweekmonster/startuptime.vim. Then you can run :StartupTime -- big-file.txt
-
Lua
tweekmonster/startuptime.vim is inaccurate. I think it doesn't take Lua into account. Don't use this plugin.
-
moonfly & nightfly colorschemes, now with faster startup
I recently had a look at startup performance. Using the startuptime plugin both moonfly & nightfly were taking around 4.5ms to load on my quad-core Linux desktop (not too bad for traditional Vimscript-based colorschemes). Some profiling did indicate that clearing highlights and resetting syntax are actually quite expensive. We really don't need to do either when loading a colorscheme at Vim start time; it is only really needed when changing colorschemes within an existing edit session. Putting in a simple guard results in moonfly & nightfly now taking only 2.5ms to startup (on my machine).
-
moonfly & nightfly colorschemes, now with expanded Neovim ecosystem support (and faster startup)
Lastly, I also had a look at startup performance. Using the startuptime plugin both moonfly & nightfly were taking around 4.5ms to load on my quad-core Linux desktop (not too bad for Vimscript-based colorschemes). Some profiling did indicate that clearing highlights and resetting syntax are actually quite expensive. We really don't need to do either when loading a colorscheme at Neovim start time; it is only really needed when changing colorschemes within an existing edit session. Putting in a simple guard results in moonfly & nightfly now taking only 2.5ms to startup (on my machine). That is quite similar to some of the nice new Lua-based Neovim colorschemes now available. A win, albeit a small one.
-
Why my config has gotten so slow?
Using the :StartupTime provided by https://github.com/tweekmonster/startuptime.vim ...
nvim-jdtls
-
Having the worst time trying to use JDTLS
I recommend that you do not configure jdtls like the other language servers, it is better to use the nvim-jdtls plugin.
-
Noob here, would neovim work for my usecase
Java is actually pretty good with Neovim, jdtls and this plugin. One of the best language servers and I'm using it on a regular base with medium to large projects, mostly spring-based. No Android though.
-
Client 2 quit with exit code 1 and signal 0 when opening a .java files
-- See `:help vim.lsp.start_client` for an overview of the supported `config` options. local config = { -- The command that starts the language server -- See: https://github.com/eclipse/eclipse.jdt.ls#running-from-the-command-line cmd = { -- 💀 'java', -- or '/path/to/java17_or_newer/bin/java' -- depends on if `java` is in your $PATH env variable and if it points to the right version. '-Declipse.application=org.eclipse.jdt.ls.core.id1', '-Dosgi.bundles.defaultStartLevel=4', '-Declipse.product=org.eclipse.jdt.ls.core.product', '-Dlog.protocol=true', '-Dlog.level=ALL', '-Xmx1g', '--add-modules=ALL-SYSTEM', '--add-opens', 'java.base/java.util=ALL-UNNAMED', '--add-opens', 'java.base/java.lang=ALL-UNNAMED', -- 💀 '-jar', '~/.local/share/nvim/mason/packages/jdtls/plugins/org.eclipse.equinox.launcher_1.6.500.v20230717-2134.jar', -- ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^ -- Must point to the Change this to -- eclipse.jdt.ls installation the actual version -- 💀 '-configuration', '~/.local/share/nvim/mason/packages/jdtls/config_linux', -- ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^ -- Must point to the Change to one of `linux`, `win` or `mac` -- eclipse.jdt.ls installation Depending on your system. -- 💀 -- See `data directory configuration` section in the README '-data', '/path/to/unique/per/project/workspace/folder' }, -- 💀 -- This is the default if not provided, you can remove it. Or adjust as needed. -- One dedicated LSP server & client will be started per unique root_dir root_dir = require('jdtls.setup').find_root({'.git', 'mvnw', 'gradlew'}), -- Here you can configure eclipse.jdt.ls specific settings -- See https://github.com/eclipse/eclipse.jdt.ls/wiki/Running-the-JAVA-LS-server-from-the-command-line#initialize-request -- for a list of options settings = { java = { } }, -- Language server `initializationOptions` -- You need to extend the `bundles` with paths to jar files -- if you want to use additional eclipse.jdt.ls plugins. -- -- See https://github.com/mfussenegger/nvim-jdtls#java-debug-installation -- -- If you don't plan on using the debugger or other eclipse.jdt.ls plugins you can remove this init_options = { bundles = {} }, } -- This starts a new client & server, -- or attaches to an existing client & server depending on the `root_dir`. require('jdtls').start_or_attach(config)
-
Foot – A fast, lightweight and minimalistic Wayland terminal emulator
I can get by with https://github.com/mfussenegger/nvim-jdtls
-
[HELP] ftplugin and lazy loading in NvChad
This and this provided no viable solutions for me
- Anyone using nvim for Kotlin development?
-
Help for configure jdtls
I tried to configure jdtls for my NeoVim I followed https://github.com/mfussenegger/nvim-jdtls install instruction. and I faced this error does anyone successfully configured jdtls ? help T ^ T
-
Adding JAR files to nvim-jdtls
Am I adding it to the wrong configuration option? Some places I see it added as a referencedLibary - https://github.com/mfussenegger/nvim-jdtls
-
Does anyone config java for neovim?
Sure. Any server that lspconfig supports will work. But for java development is better if you use nvim-jdtls. The documentation in lsp-zero has a guide on how to setup nvim-jdtls.
-
I can't seem to figure it out
Here' my java.lua for nvim-jdtls which solves the nil issue and add more features.
What are some alternatives?
lightspeed.nvim - deprecated in favor of leap.nvim
nvim-lspconfig - Quickstart configs for Nvim LSP
vim-startuptime - A plugin for profiling Vim and Neovim startup time.
eclipse.jdt.ls - Java language server
barbar.nvim - The neovim tabline plugin.
nvim-lsp-installer - Further development has moved to https://github.com/williamboman/mason.nvim!
neovim - Vim-fork focused on extensibility and usability
coc-java - Java extension for coc.nvim
hop.nvim - Neovim motions on speed!
java-debug - The debug server implementation for Java. It conforms to the debug protocol of Visual Studio Code (DAP, Debugger Adapter Protocol).
dotnvim - Neovim Lua configuration pre-configured for Java, JavaScript, Typescript etc...
mason.nvim - Portable package manager for Neovim that runs everywhere Neovim runs. Easily install and manage LSP servers, DAP servers, linters, and formatters.