CosmicNvim VS nvim-jdtls

Hover/Signature with borders https://github.com/mattleong/CosmicNvim/blob/main/lua/cosmic/lsp/init.lua

Hi everyone! I’m happy to announce that CosmicNvim now includes first-class support for 4 additional themes on top of the default for a total of 5 themes to choose from! The current selection: - [Catppuccino](https://github.com/Pocco81/Catppuccino.nvim) - [Gruvbox](https://github.com/ellisonleao/gruvbox.nvim) - [Rose-pine](https://github.com/rose-pine/neovim) - [Nord](https://github.com/shaunsingh/nord.nvim) - [Tokyonight](https://github.com/folke/tokyonight.nvim) Repo: https://github.com/mattleong/CosmicNvim (⭐️’s are very appreciated!) I’ve previously said that I wouldn’t implement first class theme support for CosmicNvim outside of the default theme… Well, I guess I changed my mind. 😅 For one, it’s probably been the most requested feature. For another, I want to be able to swap and play around with themes easily as well. My initial reason for _not_ wanting to include additional theme support was because I was worried about what sort of complexity it would bring. Turns out it’s not so bad and doesn’t overly bloat the codebase. If you have any suggestions for themes you’d like to see implemented, please feel free to drop them in the open [issue](https://github.com/mattleong/CosmicNvim/issues/25)!

If you have any suggestions for themes you’d like to see implemented, please feel free to drop them in the open issue!

I'm currently using CosmicNvim along with Bufferline. I have bufferline configured to run `:bdelete! %d` as the close command, but event calling `:bdelete` directly has the same result: neovim is closed completely rather than just the current buffer.

You can check out my config here: https://github.com/mattleong/CosmicNvim

But I didn't do enough research on Cosmic. Installation seemed simple enough. Just git clone. So I backed up my nvim folder and installed it. Carelessly went through the installer. Decided it also wasn't for me. Rather than try to uninstall it, I renamed the folder 'nvim_cosmic' just in case, reverted back to my previous nvim folder, and there's tons of lua related errors.

And currently testing out Cosmic. Just made a backup of my nvim folder first.

Take a look at CosmicNvim! (Disclaimer: I’m the author)

Can’t think of any reasons why Cosmic wouldn’t work on WSL. Haven’t tested it though.

I recommend that you do not configure jdtls like the other language servers, it is better to use the nvim-jdtls plugin.

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.

-- 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)

I can get by with https://github.com/mfussenegger/nvim-jdtls

This and this provided no viable solutions for me

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

Am I adding it to the wrong configuration option? Some places I see it added as a referencedLibary - https://github.com/mfussenegger/nvim-jdtls

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.

Here' my java.lua for nvim-jdtls which solves the nil issue and add more features.