No whitespace completion for `set_option`
Nobody has claimed this yet.
- Dominant language
- Lean
- Stars
- 9.2k
- Forks
- 990
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 175
Description
Prerequisites
Please put an X between the brackets as you perform the following steps:
- Check that your issue is not already filed:
https://github.com/leanprover/lean4/issues - Reduce the issue to a minimal, self-contained, reproducible test case.
Avoid dependencies to Mathlib or Batteries. - Test your test case against the latest nightly release, for example on
https://live.lean-lang.org/#project=lean-nightly
(You can also use the settings there to switch to “Lean nightly”)
Description
Type set_option and trigger autocompletion in an editor (VSCode and neovim tested) and no completion results are returned.
But they are properly returned for set_option t (producing all options starting with t).
Context
Reported originally here on Zulip
Steps to Reproduce
(above)
Expected behavior: [Clear and concise description of what you expect to happen]
Completion of all options if no prefix is given.
Actual behavior: [Clear and concise description of what actually happens]
No response.
Versions
[Output of #version or #eval Lean.versionString] "4.14.0"
[OS version, if not using live.lean-lang.org.] macOS 15.1 (24B83)
Additional Information
Impact
Add 👍 to issues you consider important. If others are impacted by this issue, please ask them to add 👍 to it.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue in the VSCode or Neovim editor with Lean 4.14.0, comparing set_option with set_option t; the payload names no source file or test to start from. Done means whitespace-triggered completion returns all options while prefixed completion remains correct.
Written by the indexing model from the issue text.
Assessment
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100