Merge pull request #2 from budlabs/next

added polipop command

Author: budRich

LICENSE

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2019, budRich
+Copyright (c) 2020, budRich
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

Makefile

@@ -13,6 +13,7 @@ install:
 	test -d $(INSTMAN) || mkdir -p $(INSTMAN)
 
 	install -m 0755 $(SCRIPT)  $(INSTBIN)
+	install -m 0755 polifypop  $(INSTBIN)
 	install -m 0644 $(MANPAGE) $(INSTMAN)
 .PHONY: install
 

README.md

@@ -108,7 +108,14 @@ Since only the last line of the file is the one that will
 be visible in the bar, it is possible to write and read text
 to the file and use them to f.i. store the state of a
 module. This is conveniently done by using the `--msg
-MESSAGE` option.
+MESSAGE` option.  
+
+polify is shipped with the script **polifypop**, which can
+be used to execute commands on the `--msg`line. It will only
+execute a command if it is prefixed with the word
+**POLIPOP**. And the first argument to **polifypop** needs
+to be the name of the module, it is cool to bind polifypop
+to a hotkey...
 
 ```
 $ polify --module polifyModule1 --msg "mode1" --foreground '#FF0000' this is mode one
@@ -117,6 +124,12 @@ mode1
 ```
 
 
+```
+$ polify --module polifyModule1 --msg "POLIPOP notify-send 'hello pop'" hello bar
+$ polifypop polifyModule1
+```
+
+
 `polifymodetoggler.sh`  
 
 ``` shell
@@ -228,6 +241,11 @@ UPDATES
 
 #### 2019.08.05.0
 
+Added polifypop.
+
+#### 2019.08.05.0
+
+
 Initial release.
 
 

polify

@@ -3,8 +3,8 @@
 ___printversion(){
 
 cat << 'EOB' >&2
-polify - version: 2019.08.05.8
-updated: 2019-08-05 by budRich
+polify - version: 2020.06.03.1
+updated: 2020-06-03 by budRich
 EOB
 }
 

polify.1

@@ -1,4 +1,5 @@
-.TH POLIFY 1 2019\-08\-05 Linux "User Manuals"
+.nh
+.TH POLIFY 1 2020\-06\-03 Linux "User Manuals"
 .SH NAME
 .PP
 \fB\fCpolify\fR \- Update polybar hookmodules in a safe
@@ -132,6 +133,15 @@ f.i. store the state of a module. This is
 conveniently done by using the \fB\fC\-\-msg MESSAGE\fR
 option.
 
+.PP
+polify is shipped with the script \fBpolifypop\fP,
+which can be used to execute commands on the
+\fB\fC\-\-msg\fRline. It will only execute a command if it
+is prefixed with the word \fBPOLIPOP\fP\&. And the
+first argument to \fBpolifypop\fP needs to be the
+name of the module, it is cool to bind polifypop
+to a hotkey...
+
 .PP
 .RS
 
@@ -143,6 +153,16 @@ mode1
 .fi
 .RE
 
+.PP
+.RS
+
+.nf
+$ polify \-\-module polifyModule1 \-\-msg "POLIPOP notify\-send 'hello pop'" hello bar
+$ polifypop polifyModule1
+
+.fi
+.RE
+
 .PP
 \fB\fCpolifymodetoggler.sh\fR
 
@@ -317,7 +337,7 @@ state. defaults to: /tmp/polify
 \fB\fCbash\fR \fB\fCpolybar\fR \fB\fCgetopt\fR
 
 .PP
-budRich 
+budRich https://github.com/budlabs/polify
 \[la]https://github.com/budlabs/polify\[ra]
 
 .SH SEE ALSO

polifypop

@@ -0,0 +1,9 @@
+#!/bin/bash
+
+ERX(){ >&2 echo "[ERROR]" "$*" && exit 1 ; }
+
+[[ -z $1 ]] && ERX first argument should be the name of a polify module
+
+msg=$(polify --module "$1" | head -1)
+[[ ${msg%% *} = POLIPOP ]] || exit 1
+eval "${msg#* }"