1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
|
Description: fix spelling error
Author: Josenilson Ferreira da silva <nilsonfsilva@hotmail.com>
Forwarded: not-needed
Last-Update: 2022-06-30
Index: apprise/packaging/man/apprise.1
===================================================================
--- apprise.orig/packaging/man/apprise.1
+++ apprise/packaging/man/apprise.1
@@ -69,7 +69,7 @@ return characters prior to the delivery
\fB3\fR if there was one or more Apprise Service URLs successfully loaded but none could be notified due to user filtering (via tags)\.
.IP "" 0
.SH "SERVICE URLS"
-There are to many service URL and combinations to list here\. It\'s best to visit the Apprise GitHub page \fIhttps://github\.com/caronc/apprise/wiki#notification\-services\fR and see what\'s available\.
+There are to many service URL and combinations to list here\. It\(aqs best to visit the Apprise GitHub page \fIhttps://github\.com/caronc/apprise/wiki#notification\-services\fR and see what\(aqs available\.
.SH "EXAMPLES"
Send a notification to as many servers as you want to specify as you can easily chain them together:
.IP "" 4
@@ -80,7 +80,7 @@ $ apprise \-vv \-t "my title" \-b "my no
.fi
.IP "" 0
.P
-If you don\'t specify a \fB\-\-body\fR (\fB\-b\fR) then stdin is used allowing you to use the tool as part of your every day administration:
+If you don\(aqt specify a \fB\-\-body\fR (\fB\-b\fR) then stdin is used allowing you to use the tool as part of your every day administration:
.IP "" 4
.nf
$ cat /proc/cpuinfo | apprise \-vv \-t "cpu info" \e
@@ -113,7 +113,7 @@ $ apprise \-vv \-t "School Assignment" \
.fi
.IP "" 0
.SH "CUSTOM PLUGIN/NOTIFICATIONS"
-Apprise can additionally allow you to define your own custom \fBschema://\fR entries that you can trigger on and call services you\'ve defined\.
+Apprise can additionally allow you to define your own custom \fBschema://\fR entries that you can trigger on and call services you\(aqve defined\.
.P
By default \fBapprise\fR looks in the following local locations for custom plugin files and loads them:
.IP "" 4
@@ -139,7 +139,7 @@ def my_wrapper(body, title, notify_type,
.fi
.IP "" 0
.SH "CONFIGURATION"
-A configuration file can be in the format of either \fBTEXT\fR or \fBYAML\fR where [TEXT][textconfig] is the easiest and most ideal solution for most users\. However YAML \fIhttps://github\.com/caronc/apprise/wiki/config_yaml\fR configuration files grants the user a bit more leverage and access to some of the internal features of Apprise\. Reguardless of which format you choose, both provide the users the ability to leverage \fBtagging\fR which adds a more rich and powerful notification environment\.
+A configuration file can be in the format of either \fBTEXT\fR or \fBYAML\fR where [TEXT][textconfig] is the easiest and most ideal solution for most users\. However YAML \fIhttps://github\.com/caronc/apprise/wiki/config_yaml\fR configuration files grants the user a bit more leverage and access to some of the internal features of Apprise\. Regardless of which format you choose, both provide the users the ability to leverage \fBtagging\fR which adds a more rich and powerful notification environment\.
.P
Configuration files can be directly referenced via \fBapprise\fR when referencing the \fB\-\-config=\fR (\fB\-c\fR) CLI directive\. You can identify as many as you like on the command line and all of them will be loaded\. You can also point your configuration to a cloud location (by referencing \fBhttp://\fR or \fBhttps://\fR\. By default \fBapprise\fR looks in the following local locations for configuration files and loads them:
.IP "" 4
|
