Selective use of complete_options for single hashes #91
Replies: 2 comments
-
Dealing with Most if not all CLI programs that support What you can do, is something like this: cli:
- --user=
- --env=dev
- --env=prod
- --env=stage Meaning: Keep arg and its value as one completion. The There may be a way to add support for "terminate without space" by allowing a syntax like this: cli:
- --user=$ # <-- some terminating symbol
- --env=dev
- --env=prod
- --env=stage but I will have to see if this can be done without overcomplicating it. |
Beta Was this translation helpful? Give feedback.
-
In my special case Install one or more eisfair packages usage: options:
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I'm glad to find your tool for creating a completion file for my fritzboxtool (https://github.com/MarcusRoeckrath/fbtr64toolbox). It works fine.
With this experience I want to make more completion files for other tools mainly for the scripts of the german linux server distribution eisfair, which I'm part of the main team.
Our mainly packet managing programm uses options like
--option=value
With
completely_options:
complete_options: -o nospace
at top of the yaml file, tab completion will put the cursor directly behind the word but I want the the cursor to be placed after a space on normal options and directly behind the "=" on options described above.
Is there a way to prepare the yaml file in a way to reflect this purpose?
Many thanks for the tool.
Marcus
Beta Was this translation helpful? Give feedback.
All reactions