xbattext.ms: Explain ALERT constant

1 files changed, 24 insertions, 1 deletions

diff --git a/xbattext.ms b/xbattext.ms
index 6acfd80..e000dd3 100644
--- a/xbattext.ms
+++ b/xbattext.ms
@@ -46,6 +46,10 @@ is needed in order to inspect the battery status on NetBSD.
 .Re xbattext.c:/^\/\* interval in seconds/
 .LP
 By default, the battery status is checked every ten seconds.
+.Re xbattext.c:/^\/\* low battery level/
+.LP
+By default, the battery level is considered to be low
+if it is below 30 percent.
 .Re xbattext.c:/^struct res/
 .LP
 Two structures are created to access the application's resources:
@@ -65,7 +69,7 @@ For more information about resource management and the structure of the
 .I XtResource
 type, see
 .nh
-http://lesstif.sourceforge.net/doc/super-ux/g1ae03e/part1/chap9.html.
+http://lesstif.\:sourceforge.net/doc/super-ux/g1ae03e/part1/chap9.html.
 .hy
 .FE
 .Re xbattext.c:/"alertFontList"/
@@ -259,3 +263,22 @@ which at the end is registered through the
 function to occur in
 .CW INTERVAL
 seconds.
+.Rr
+.sp \(PN
+.LP
+That is the totality of the
+.I xbattext
+source
+(almost; a long comment at the beginning of the file, explaining
+what the program does and how it should be compiled, was excluded).
+Hopefully, it shows that graphical UNIX programming is nothing to be scared of.
+While Xlib, Xt and Xm tend nowadays not to be considered
+.Q "best practice"
+(whatever that means),
+they have a low barrier to entry,
+require little resources from the computer and
+are often installed by default on UNIX systems.
+It is better to use worse practices to create something
+than to use best practices and create nothing at all;
+if those are the alternatives,
+then perhaps best practices aren't.