Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Omni completion doesn't work: complete/completion mismatch

Open
#56 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
35/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
vim
Domain
tooling

Research direction

Start in autoload/rescript.vim at the linked omni-completion call, then compare its command with the rescript-editor-analysis CLI entry point referenced in the issue. Done means the Vim completion request uses the analyzer's expected command and omni completion works successfully.

Written by the indexing model from the issue text.

Description

vim-rescript tries to use complete:

https://github.com/rescript-lang/vim-rescript/blob/faeeb2deef1ad0ec67fc892ceeb9949f3bf2d77c/autoload/rescript.vim#L346

The underlying rescript-editor-analysis.exe expects completion:

https://github.com/rescript-lang/rescript-vscode/blob/master/analysis/src/Cli.ml#L66

Dominant language
Vim Script
Stars
164
Forks
17
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rescript-lang/vim-rescript

All issues in rescript-lang/vim-rescript

Similar issues

More DevTools issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.