React to various system events by creating files with specific names.

1. Triggrd is a spoon (plugin) for Hammerspoon. You will need to download and install it first. If you already have and use Hammerspoon, ignore the next step.
2. Make sure you have a .hammerspoondirectory in your home folder, and an init.lua file in it.
3. Open Triggrd.spoon or copy it to ~/.hammerspoon/spoons/
4. Somewhere within your init.lua file, add the following lines:

hs.loadSpoon("Triggrd")
spoon.Triggrd:start()

1. There is a set of example event automations in the My Example Triggrd Automations directory in this repository. Copy or symlink it into your documents folder if you wish, making sure to remove the word "Example".

Triggrd includes a utility to migrate SoundNote soundpacks to the Triggrd format. To access it, click on the Triggrd menu on the menu bar and select "Migrate SoundNote soundpack..."

Note for blind users: The Triggrd menu in menu extras is spoken as "Hammerspoon: Triggrd". There seems to be nothing I can do about that for now.

• All of your automations will be in a path of your choosing. By default, this is ~/documents/My Triggrd Automations. You can change this by modifying the userAutomationsPath variable in the spoon's init.lua.
• Any file or folder in the automations directory whose name beginns with a dot (.) will be ignored by Triggrd.
• Every event is composed of several tags. To react to an event, you can create a file in the automations directory or any of its subdirectories with a name composed of tags separated by dots (.). The list of supported extensions is down below. For example, app.launched.wav, battery.20percent.down.lua, or power.txt.
• An automation will only trigger if the event contains all of its tags. volume.wav will play every time any event happens with any volume, app.launched.Safari will trigger when Safari is launched, battery.40percent.txt will be spoken when the battery reaches 40% either charging or discharging.

• Audio files: Any file format supported by hs.sound.
• Lua scripts: They will receive an event data table as a vararg which will contain, at the very least, a reference to the Triggrd object.
• TXT files: They will be spoken by the default system voice. Some of them may let you use formatstrings to add relevant data into the spoken text.

All of these events will include a tag with the name of the app in question.

TXT files may also reference two formatstring arguments, the name of the app and the event type.

• activated (gets focus)
• deactivated (loses focus)
• hidden
• unhidden
• launching
• launched
• terminated (quit)

TXT files may also reference a single formatstring argument, the event type.

• screensaverDidStart
• screensaverWillStop
• screensaverDidStop
• screensDidLock
• screensDidUnlock
• screensDidWake
• screensDidSleep
• sessionDidBecomeActive
• sessionDidResignActive
• systemWillSleep
• systemDidWake
• systemWillPowerOff

All of these events will include a tag with the name of the USB device in question.

TXT files may also reference two formatstring arguments, the name of the device and the event type.

• added (connected)
• removed (disconnected)

The second tag may be the word space followed by the number of the new space. This number will also be passed as a formatstring argument to txt files.

The second tag may be the contents of the pasteboard. These will also be passed as a formatstring to txt files.

• xpercent, where x is a battery percentage
• up, when the change in percentage is upwards
• down, for the opposite
• charging, for when the battery starts charging. Will not include percentage tags
• notCharging, for the opposite

• onAC
• onBattery
• offLine

This event seems to fire whenever a change occurs in the screen configuration or layout.

• didMount
• willUnmount
• didUnmount
• didRename

The "roadmap" is "detailed" here. Any suggestions and/or pull requests are welcome.

• @GRMrGecko for creating SoundNote, which became an invaluable tool for me and many other blind mac users and inspired Triggrd.
• @Mikholysz for writing the first few lines of code, and finally getting me to work on this.
• My good friends of Currently Untitled Audio for the example set, which we will be expanding as new events come in.