Experimental Option Tracking: background-completions
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 40.5k
- Forks
- 2.3k
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 85
Description
Identifier
background-completions
Introducing PR
#18764
Status
opt-out
Description
background-completions (added in #18764) runs REPL completions on a worker thread so typing never blocks.
The async path is the default under test, and disabling it restores the pre-#18334 blocking behavior so custom completers can drive interactive child processes ($candidates | fzf, see #18771).
This issue tracks how the option ends its life. Either:
- the async path stabilizes as the only behavior once interactive completers have a supported path of their own, and the option is removed, or
- problems surface that keep the blocking path necessary, and the option graduates to a proper config setting.
Related
#18764
#18334
#18771
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
Start with PR #18764 and the related issues #18334 and #18771 to understand the background-completions option, its worker-thread path, and the blocking behavior needed by custom completers. Done means determining whether the async path can become the only behavior or whether the option should graduate to a supported configuration setting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100