ddc.vim VS ale

Have a look at ddc.vim and denops.vim

There is shougo/ddc.vim by the same author

e.g:https://github.com/Shougo/ddc.vim

I use dense-analysis/Ale for code linting. Lately, I moved to update my tab completion from deoplete to Shougo/ddc.vim; the autocompletion of Ale is routed to ddc using statiolake/ddc-ale but the Ale autocomplete leaves things to be desired.

I was looking at ddc.vim and it looked somewhat similar to nvim-cmp. There's also multiple sources for it with no inbuilt ones. So, I was wondering if anyone has used both of them and could provide some pointers on a rough comparison between the both. Also, if there's any config file with sources for lsp, buffer, and other useful ones already setup, then could you share that too?

Sadly deoplete doesn't play well with 'some' asynchronous plugin sources (ex: vim-iced). I still got to try ddc.vim to see if things are easier and if middle word completion is done right.

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

Support for code quality tools are provided by the ALE plugin. These are supported for PHP:

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.

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

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

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

At some of those syntax things neovim behaves better, and like. But there is https://github.com/dense-analysis/ale.

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

I'm not doing much of anything in Python, but according to :help ale-python-pylint: