Skip to content

Commit 1637526

Browse files
committed
explain usage a bit better
add more details on how the files could/should be sourced. add info on how to use them permanently. thanks to asaveljevs for the inspiration.
1 parent b858208 commit 1637526

File tree

1 file changed

+10
-2
lines changed

1 file changed

+10
-2
lines changed

README.md

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,9 +3,9 @@ Zabbix Bash Completion
33

44
Bash completion for Zabbix commands
55

6-
To try this out, source the file. For example:
6+
To try this out, source the files. For example:
77

8-
$ . zabbix_get-completion
8+
$ . zabbix_get-completion; . zabbix-utils-completion
99
$ zabbix_get -<tab><tab>
1010

1111
For zabbix_get, item key completion is available. Available item keys are hardcoded. If the currently completed key ends
@@ -41,6 +41,14 @@ For all daemons, runtime options are completed. For log level changing:
4141
For all completions, parameters are supported via space. Specifying them right away or via an equal sign (like -pvalue
4242
or --param=value) is not supported.
4343

44+
# Installing
45+
46+
Simple testing can be done by sourcing the files. Completion for get and sender depends on zabbix-utils-completion.
47+
Completion for agentd, server and proxy depends on zabbix-daemons-completion.
48+
49+
To make Zabbix command completion available permanently, place all the files in /etc/bash_completion.d/ and start a new
50+
shell session.
51+
4452
# Requirements
4553

4654
* awk

0 commit comments

Comments
 (0)