split up "normal completion" and "fuzzy completion integration"
- Dominant language
- Go
- Stars
- 83k
- Forks
- 2.9k
- Avg merge
- 17h 8m
- Merged PRs (30d)
- 10
Description
- [x] I have read through the manual page (`man fzf`)
- [x] I have the latest version of fzf
- [x] I have searched through the existing issues
## Info
- OS
- [x] Linux (NixOS)
- [ ] Mac OS X
- [ ] Windows
- [ ] Etc.
- Shell
- [x] bash
- [ ] zsh
- [ ] fish
## Problem / Steps to reproduce
I think it would be good to split up the `completion.bash` file, and differentiate between the regular tab completion of options to fzf, which can be installed inside the normal bash completion directory like any completion script on the one hand, and the fuzzy completions of every other command, using fzf to display the possibilities on the other hand.
This enables users to opt for not using the fzf fuzzy completion for commands, but they can still get proper completion of fzf options. It also makes the packaging process easier, or at least more standardized.
I think the same thing also goes for zsh, but i haven't checked.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading completion.bash and the fzf manual's completion sections. Separate regular fzf option completion from fuzzy completion for other commands, so the former can be installed in the standard Bash completion directory while the latter remains optional. Check whether the same separation is needed for zsh, as suggested in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bash
- Domain
- cli
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100