From 16375263d8b2df6b8538a4dce92920e92398acb0 Mon Sep 17 00:00:00 2001 From: richlv Date: Wed, 28 Oct 2015 16:50:58 +0200 Subject: [PATCH] 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. --- README.md | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index e8eeb9f..578dbea 100644 --- a/README.md +++ b/README.md @@ -3,9 +3,9 @@ Zabbix Bash Completion Bash completion for Zabbix commands -To try this out, source the file. For example: +To try this out, source the files. For example: - $ . zabbix_get-completion + $ . zabbix_get-completion; . zabbix-utils-completion $ zabbix_get - 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: For all completions, parameters are supported via space. Specifying them right away or via an equal sign (like -pvalue or --param=value) is not supported. +# Installing + +Simple testing can be done by sourcing the files. Completion for get and sender depends on zabbix-utils-completion. +Completion for agentd, server and proxy depends on zabbix-daemons-completion. + +To make Zabbix command completion available permanently, place all the files in /etc/bash_completion.d/ and start a new + shell session. + # Requirements * awk