diff options
author | Tanaka Akira <akr@users.sourceforge.net> | 1999-09-09 14:10:01 +0000 |
---|---|---|
committer | Tanaka Akira <akr@users.sourceforge.net> | 1999-09-09 14:10:01 +0000 |
commit | 2f36613557a4d33b5706cd9335ff0a4c3b6f1c91 (patch) | |
tree | 6bfbe3da09b06fff2864b8798fe2bac09c1526b9 /Etc/completion-style-guide | |
parent | 415b5f4cc2ef54943d178bef0c55b2517afc6904 (diff) | |
download | zsh-2f36613557a4d33b5706cd9335ff0a4c3b6f1c91.tar.gz zsh-2f36613557a4d33b5706cd9335ff0a4c3b6f1c91.tar.xz zsh-2f36613557a4d33b5706cd9335ff0a4c3b6f1c91.zip |
zsh-workers/7747
Diffstat (limited to 'Etc/completion-style-guide')
-rw-r--r-- | Etc/completion-style-guide | 6 |
1 files changed, 5 insertions, 1 deletions
diff --git a/Etc/completion-style-guide b/Etc/completion-style-guide index 949ae1a9f..5bc289b9b 100644 --- a/Etc/completion-style-guide +++ b/Etc/completion-style-guide @@ -35,7 +35,11 @@ For now this is just a list of things one should or shouldn't do. configuration key to allow users to select the behavior they prefer. Names for configuration keys should look like `prefix_name', where `prefix' is the (probably abbreviated) name of your function - and `name' describes what can be configured. + (without any leading underscore) and `name' describes what can be + configured. + If you want to have this completion function to be included in the + distribution, it would help if you describe the configuration key + at the end of the `compsys.yo' manual. When testing the values of configuration keys, the empty string should result in the same behavior as if the key were unset. This can be achieved by the test `[[ -n "$compconfig[prefix_name]" ]]'. |