Compare commits

..

No commits in common. "b3955ffe260fdee269f2e09463d1b1c32c6eddd3" and "40f09228fe9c05d17e3e7262f2ee31198601d8d0" have entirely different histories.

2 changed files with 9 additions and 5 deletions

View file

@ -29,13 +29,17 @@ This is something I was inspired to do after writing `clipurr`… "purr", like a
So I thought I'd rename everything else to conform to this amazing naming convention… cool eh‽
### Example:
### Example in `dmenu`:
![wm_tools](https://user-images.githubusercontent.com/31094984/167123173-ee8092a2-d5ab-47b4-b207-ced328072cc0.gif)
![dmenu_tools](https://user-images.githubusercontent.com/31094984/167123173-ee8092a2-d5ab-47b4-b207-ced328072cc0.gif)
### Example of `cmd_wrappurr` with `clipmenu`
![command_wrap](https://user-images.githubusercontent.com/31094984/167122436-eea0be88-a929-46e8-9b4d-cb677dcb129c.gif)
## How to compile
There are some configuration variables explicit to me, you'll need to change them for you for them to be useful I imagine.
Configuration variables are compile - there are no config files or runtime parameters
Configuration variables are compile - there are no config files or runtime parameters (except for "rofi")
Each tool is compiled separately, for example:
```sh
@ -52,10 +56,10 @@ or
```
## How to use
Personally, I have these bound to key combinations in i3 and sway.
Personally, I have these bound to key combinations in i3.
In fact, I have a seperate `bindsym` mode in which all these
tools are accessible i.e. `$mod+i` to get to "info" mode then `p` to show pingclock.
It's completely up to you how to run them, they're just simple CLI tools.
It's completely up to you how to run them, they're just simple CLI tools really.
### You can also set the volume and brightness levels by typing a numeric figure into the dmenu/rofi input box

Binary file not shown.

Before

Width:  |  Height:  |  Size: 22 KiB