Add documentation for environment variables passed to scripts

This commit is contained in:
fwsmit 2021-01-21 16:40:32 +01:00
parent 0d5cbfcfce
commit 52134ab8ce

View File

@ -869,11 +869,22 @@ Within rules you can specify a script to be run every time the rule is matched
by assigning the 'script' option to the name of the script to be run. by assigning the 'script' option to the name of the script to be run.
When the script is called details of the notification that triggered it will be When the script is called details of the notification that triggered it will be
passed via command line parameters in the following order: appname, summary, passed via environment variables. The following variables are available:
body, icon, urgency. B<DUNST_APP_NAME>, B<DUNST_SUMMARY>, B<DUNST_BODY>, B<DUNST_ICON_PATH>,
B<DUNST_URGENCY>, B<DUNST_ID>, B<DUNST_PROGRESS>, B<DUNST_CATEGORY>,
B<DUNST_STACK_TAG>, B<DUNST_URLS>, B<DUNST_TIMEOUT>, B<DUNST_TIMESTAMP>
and B<DUNST_STACK_TAG>.
Where icon is the absolute path to the icon file if there is one and urgency is Another, less recommended way to get notifcations details from a script is via
one of "LOW", "NORMAL" or "CRITICAL". command line parameters. These are passed to the script in the following order:
B<appname>, B<summary>, B<body>, B<icon_path>, B<urgency>.
Where B<DUNST_ICON_PATH> or B<icon_path> is the absolute path to the icon file
if there is one. B<DUNST_URGENCY> or B<urgency> is one of "LOW", "NORMAL" or
"CRITICAL". B<DUNST_URLS> is a newline-separated list of urls associated with
the notification.
Note that some variables may be empty.
If the notification is suppressed, the script will not be run unless If the notification is suppressed, the script will not be run unless
B<always_run_scripts> is set to true. B<always_run_scripts> is set to true.