- single pre-compiled binary
- uses layed config, getting settings from
/etc/default/yapc.yaml,~/.config/yapc.yamlor the environment - only supports pushover
- bash shell hook (WIP)
- Linux only
Download latest binary from release page, or to compile from source:
cargo build --releaseCopy it to your path.
Then:
$ yapc send --help
sends a message
Usage: yapc send [OPTIONS] <BODY> [SUBJECT]
Arguments:
<BODY>
[SUBJECT]
Options:
-u, --url <URL>
-t, --url-title <URL_TITLE>
-p, --prioity <PRIOITY>
-s, --sound <SOUND> [possible values: pushover, bike, bugle, cashregister, classical, cosmic, falling, gamelan, incoming, intermission, magic, mechanical, pianobar, siren, spacealarm, tugboat, alien, climb, persistent, echo, updown, vibrate, none]
-h, --help Print helpyapc has support for automatically sending notifications when long
running commands finish in bash and zsh. In bash it emulates zsh's preexec and
precmd functionality with rcaloras/bash-preexec <https://github.com/rcaloras/bash-preexec>_.
To enable it add the following to your .bashrc or .zshrc:
eval "$(yapc shell-integration bash)"
# or
eval "$(yapc shell-integration zsh)"To avoid unnecessary notifications:
- listed programs are excluded;
- notifications are not sent for commands that return in less then 60 seconds
The defaults are set is in shell-hook and may be overridden as follows:
# e.g. increase default notification threshold to 90 seconds
export AUTO_YAPC_DONE_LONGER_THAN=90
# e.g. set ignore list to following
export AUTO_YAPC_DONE_IGNORE="vim screen meld"The following places are serched for configuration (in order of priofity):
- the environment variables
YAPC_APP_TOKEN,YAPC_USER_KEY,YAPC_PRIOTITY,YAPC_SOUND ~/config/yapc.yaml/etc/default/yapc.yaml
The structure of the yaml file is as follows:
---
app_token: your pushover app token
user_key: your pushover user key
priotity: 0
sound: bike