yabs.nvim
nvim-jdtls
yabs.nvim | nvim-jdtls | |
---|---|---|
12 | 75 | |
202 | 934 | |
- | - | |
0.0 | 7.0 | |
4 months ago | 2 months ago | |
Lua | Lua | |
GNU Affero General Public License v3.0 | 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.
yabs.nvim
-
toggletasks.nvim - toggleterm+telescope task runner with JSON/YAML configs
toggletasks.nvim is a task manager inspired by yabs.nvim and projectlaunch.nvim. In fact initially I wanted to extend projectlaunch.nvim, but then I decided that I want to make too many changes and it should be a separate plugin. A small comparison is in the README.
-
Any plugins for project local building and makeprg?
Or maybe this: https://github.com/pianocomposer321/yabs.nvim
-
Should a plugin rewrite be a new repository, or a new branch on the existing one?
I'm the author of https://github.com/pianocomposer321/yabs.nvim. I've been thinking for a while that it might be time for either a major refactor or a complete rewrite, and this last week I decided to just do it. I won't get into all the reasons why I thought this was a good choice (if y'all want to hear why, I'll probably explain in a separate post when I announce that the new version is done), but my question is this: when I'm ready to put the new version up on github, should it be in a new repository under a new name, or under a new branch in the current version? It seems that most other people have always done it under a new repository, but then I'd have to come up with a new name (😬), and it wouldn't have the same discoverability as the original repo did, at least at first (because it would start with no stars). On the other hand, if I made it just a new branch, I'd have to add a deprecation message to the current main branch saying that the new version will eventually take it's place, and that will be a small but annoying breaking change for existing users who don't want to switch to the new version.
- How to compile and execute C++ cmake, make?
-
How do I compile and run Java with NeoVim? (for learning Java)
I haven't tried it myself yet but perhaps yabs.nvim is what you're looking for?
-
[Plugin] BuildTask.nvim: Run tasks similar to VScode
I current use yabs.nvim, which is very similar to what you're trying to do.
-
ToggleTerm with YABS
I would like to setup tasks with YABS that are opened inside a ToggleTerm floating terminal window.
-
Thanks everyone! (Yabs.nvim makes it to 100 stars!)
Hello everyone, I'm the author of yabs.nvim. For those of you who don't know, yabs adds functionality similar to vscode's tasks system to neovim. In any case, we recently passed 100 stars on github, and this milestone seemed like an appropriate time to thank everyone who's helped get to that point.
- yabs.nvim - Yet another build system for neovim, written in lua
-
How to run C++ from vim in an external terminal window with ability to add input.
I wrote two plugins for exactly this purpose. One is pianocomposer321/yabs.nvim, which allows you to specify which commands (vim ex commands, or external commands) should be run for which filetype, and also where the output should go (the quickfix list, the terminal, etc). The other is pianocomposer321/consolation.nvim, which allows for easy management of terminals. These plugins will work independently of each other, but they work best together.
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?
code_runner.nvim - Neovim plugin.The best code runner you could have, it is like the one in vscode but with super powers, it manages projects like in intellij but without being slow
nvim-lspconfig - Quickstart configs for Nvim LSP
vim-dispatch - dispatch.vim: Asynchronous build and test dispatcher
eclipse.jdt.ls - Java language server
neovim-java - Neovim Java client library. Provides multiple interfaces for communicating with Neovim instance via multiple different protocols. - Moved to https://codeberg.org/neovim-java/neovim-java
nvim-lsp-installer - Further development has moved to https://github.com/williamboman/mason.nvim!
asynctasks.vim - :rocket: Modern Task System for Project Building, Testing and Deploying !!
coc-java - Java extension for coc.nvim
consolation.nvim - A general-purpose terminal wrapper and management plugin for neovim, written in lua
java-debug - The debug server implementation for Java. It conforms to the debug protocol of Visual Studio Code (DAP, Debugger Adapter Protocol).
toggletasks.nvim - Neovim task runner: JSON/YAML + toggleterm.nvim + telescope.nvim
mason.nvim - Portable package manager for Neovim that runs everywhere Neovim runs. Easily install and manage LSP servers, DAP servers, linters, and formatters.