nvim-dap-ui
ale
nvim-dap-ui | ale | |
---|---|---|
48 | 133 | |
2,231 | 13,288 | |
- | 0.4% | |
7.0 | 8.7 | |
5 days ago | 2 days ago | |
Lua | Vim Script | |
MIT License | BSD 2-clause "Simplified" 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-dap-ui
-
I've crated my own zen mode plugin, but how and why?
I use https://github.com/shortcuts/no-neck-pain.nvim or https://github.com/rcarriga/nvim-dap-ui
-
dapui and lualine visual/aesthetic configuration
However, this is what my current setup looks like. 1. No titles. 2. lualine at the very bottom. Any suggestions? I tried reading the docs (dapui, lualine), but am kinda lost. I am not sure what I did wrong?
-
NeoZoom.lua: nvim-dap support pre-release
I want to see those widgets (stacks/scopes/repl/etc) in a floating window to protect my neck, since I always felt that any custom layout of nvim-dap-ui can break my neck. While nvim-dap-ui also supports floating window, I believe it's still in some early stage that I'm happy to do it myself.
- Need help with Telescope Grep:
-
What has been people's experience with nvim-dap? Or integrating the debugging experience within Neovim itself?
When i set it up for c++, I didn't have hard time to set it up because there's a wiki guide on the repo. Lastly, I just to set it up for fun purposes only and it'll great if you use it with nvim-dap-ui.
-
JDTLS (maybe) issue with neovim 0.9
That's a known issue, it's been idle for a while as no one has been able to find a reproduction. According to the latest comment on that thread, it seems to resolved on nightly.
- Rust, RR, Neovim: A perfect debug combination
-
Run code / something like the VSCode F5
use nvim dap and nvim dap ui
-
plugin announcement | base16-nvim featuring hot loading of plugins set by base16-shell
I'm using many plugins and the only one that didn't work out of the box is feline and nvim-dap-ui.
-
Advice on moving from Emacs to Neovim
nvim-dap supports vscode's launch.json. Also see nvim-dap-ui.
ale
-
A decent VS Code and Ruby on Rails setup
I saw no mention of RBS+Steep, the latter providing a LSP. I use it a lot and very much like it, although it's still young and needs love, but it's making good, steady progress! I've been very pleasantly surprised by some of the crazy things Steep can catch, completely statically!
You appear to be working on projects with Sorbet (which I tried to like but found it fell short in practice, notably outside of the app use case i.e it's mostly useless for gems) so it may be a tall order to try on those. Maybe you can give RBS+Steep a shot on some small project?
RBS: https://github.com/ruby/rbs
RBS collection (for those gems that don't ship RBS signatures in `sig`, integrates with bundler): https://github.com/ruby/gem_rbs_collection
Steep: https://github.com/soutaro/steep
VS Code: https://github.com/soutaro/steep-vscode
Sublime Text: https://github.com/sublimelsp/LSP
Vim (I'm working on it): https://github.com/dense-analysis/ale/pull/4671
-
Laravel code-quality tools
Support for code quality tools are provided by the ALE plugin. These are supported for PHP:
-
Embracing Common Lisp in the Modern World
I mostly agree, though I find Allegro and LispWorks severely lacking in areas too. The companies themselves don't seem to care much about their IDEs. Certainly not in the way JetBrains cares about IntelliJ.
Tucked away in the McCLIM project is Clouseau, which you can quickload and use as a normal user: https://codeberg.org/McCLIM/McCLIM/src/branch/master/Apps/Cl... One small cool thing it does is if you inspect a complex number it will also draw a little x-y vector. (Though trying it out again just now it's overlapping with the text... maybe I should file a bug, but I've only now just learned they moved off github, and I'm not going to make a codeberg account. Friction wins this round.) It does take a while to first compile and load all the dependencies, especially 3bz, another weakness of at least our free Lisps; AFAIK there's still no equivalent of make -j for compiling systems.
I'm a happy vim user (though there is some jank with slimv, admittedly, but it's mostly prevalent around multiple thread situations) and setup the command ,ci to call my own clouseau-inspect function; it just inspects a symbol with clouseau instead of slimv's inspector. Also have a janky watch/unwatch pair of functions that just refreshes the inspector every second. (https://github.com/Jach/dots/blob/master/.sbclrc#L113 if curious, some other junk in .swank.lisp and .vimrc too, and there's https://github.com/dense-analysis/ale/issues/4061 to call sblint on your project...)
But better forms of these sorts of graphical tools are what I hope to one day see more of and are how the free Lisps can close the gap in this area with the commercial Lisps. I believe there's not much Allegro can do that poking around SBCL can't do, but for many things it's just nicer to have a GUI. Want to explore all the symbols and values in a package? Easy enough to script that, but not as nice as just having a table of symbols, and even nicer if you can set watches on some of them. None of the tools need to be tightly integrated with a single IDE either, because all the stuff necessary to debug Lisp is in the running Lisp itself. It's just that the GUI situation continues to suck.
LSP has gotten more popular with other languages and editors, sometimes I wonder if the acronym was made as an inside joke because it's basically how Lisp + Slime/Swank have worked...
-
A Humble Request for Assistance Maintaining ALE
Hello Everyone! w0rp here. I thought I'd ask on Reddit if there's anyone out there would like to help maintain ALE. It would be nice to have another willing volunteer who is up for providing relevant feedback on PRs, answering common questions, merging good PRs, and managing GitHub issues. I'll mention to anyone interested that I have a general policy of never closing issues, no matter how old, unless they are actually either solved or invalid. I bear no compulsions to ensure an that a number of issues, which is arbitrary, remains low. I have a relatively simple vetting process, which mostly just requires building trust over time.
-
Static Analysis Tools for C
A similarly useful list is vim's famous ALE plug-in's list of supported linters:
* https://github.com/dense-analysis/ale/blob/master/supported-...
While less comprehensive¹, this is my go-to list when I start working with a new language. Just brew/yum/apt installing the tool makes it work in the editor²
¹this list mostly has foss,static analyzers, however anyone can contribute (mine was the gawk linting)
²alright,there are some. Tools that might need some setup
-
Tell HN: Vim Has Autocomplete
Ctrl-X Ctrl-L is line based completion, see :help CTRL-X_CTRL-L for details.
:help ins-completion gets the useful docs, Vim's own docs are very good and worth spending some time learning how to use, so you can learn Vim itself better.
Another favorite of mine is 'gf' to open the filename under the cursor, very useful combined with ^X ^F.
Omni completion is also useful: https://vim.fandom.com/wiki/Omni_completion although you're better off with plugin that uses LSP now, for example https://github.com/dense-analysis/ale
-
LazyVim
FWIW, I still use regular vim with ale [0] and it does everything I want. It formats files with Black and isort, shows ruff and pyright errors, supports jumping to definitions, and has variable information available on hover. I have collected my config over the past several years, but I pretty rarely encounter errors with it.
[0]: https://github.com/dense-analysis/ale [1] https://github.com/CGamesPlay/dotfiles/blob/master/files/.co...
-
How to configure vim like an IDE
At some of those syntax things neovim behaves better, and like. But there is https://github.com/dense-analysis/ale.
-
Vim users who work without any plugins, how does your vimrc look like?
I replace ALE with :!, like :! %. If the linter output is compatible with default errorformat , then I do :! % > /tmp/linter.txt then :cgetfile (or in one-go: :cgetexpr systemlist(''))
-
Per project settings for linters used by ALE, how to do it the right way?
I'm not doing much of anything in Python, but according to :help ale-python-pylint:
What are some alternatives?
node-vim-debugger - node.js step by step debugging from vim
vim-lsp - async language server protocol plugin for vim and neovim
telescope-dap.nvim - Integration for nvim-dap with telescope.nvim
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
vimspector - vimspector - A multi-language debugging system for Vim
YouCompleteMe - A code-completion engine for Vim
vim-test - Run your tests at the speed of thought
nvim-lspconfig - Quickstart configs for Nvim LSP
DAPInstall.nvim - 🦆 A NeoVim plugin for managing several debuggers for Nvim-dap
syntastic - Syntax checking hacks for vim
nvim-dap - Debug Adapter Protocol client implementation for Neovim
nvim-lint - An asynchronous linter plugin for Neovim complementary to the built-in Language Server Protocol support.