mnowotnik / extra-fzf-completions

Simple, seamless fzf-based completions for a few applications

Michał Nowotnik

Software developer and consultant 💻

Enthusiastic about automating boring processes and leveraging machines to make our work faster and lives more pleasant.

Personal webpage

https://mnowotnik.com

Contact

You can find my email either on the github profile or on my webpage.

extra-fzf-completions's Issues

[Feature] Support completions for every action in docker

Currently some action completions are not available.

[Idea] Add intelligent completion to the history-based completion

#5 could be extended to include intelligent completion based on some classifier , e.g. naive bayes.

[Feature] Add generic completions for kubectl for any type of resource

Completions for kubectl of type:

kubectl <action> <resource_type>/**

should be supported. It is easy to fetch completion list for them
by parsing prefix.

[Feature] Support for git

An idea for a git support is completion of recently commited branches in a command:

git checkout b:**<TAB>

[Feature][Idea] Parsing user command history for specific commands

A user could be able to activate history parsing for certain commands to provide him with
completion of values for parameters in the current command.
For example:

curl -H %%<TAB>

would show the list of every header in user's history.
Drawbacks:

• could be a cpu-intensive operation, but it's unlikely,
• history has a limit
• using the same prefix for command completion and history-based command completion can be confusing for a user

[Feature] Support for mvn

mvn test -Dtest=<test class> could be made much less cumbersome by allowing a user to find class in a fuzzy search and complete -Dtest=** only with a class name. The completion should be possibly to perform multiple times in a case a user wants many test classes separated by comma: -Dtest=<test_class1>,<test_class2>.