Load Sample Triggers

Blue Synergy ships with a curated set of example triggers covering the most common use cases: an email signature, a meeting template, datetime insertion, a PowerShell public-IP lookup, a cmd local-IP lookup, clipboard references, glue helpers, and more.

On a fresh install these are seeded automatically the first time the app starts. After that — or if you’ve deleted some and want them back, or want to preview the latest canonical versions after an update — you can reload them from the menu.

How to load them

File → Load Sample Triggers…

This opens the standard Trigger Import dialog with every shipped sample preloaded as a row. You get the same interface you’d see importing any Blue Synergy YAML file:

  • Checkbox per row — pick exactly which samples to add.
  • Conflict indicator — samples whose keyword already exists in your trigger list are flagged. Check the “Overwrite” box per row to replace; leave unchecked to keep your existing version.
  • Preview — keyword, description, and first step at a glance before you confirm.
  • Undo — if the import turns out wrong, one click restores your previous state.

Click Import to apply; click Cancel to back out without changes.

The shipped set

Keyword Type Purpose
;sig TXT Email signature
;addr TXT Home address
;dt TXT Current date & time
;ty TXT Thank-you reply
;mtg TXT Meeting template
;fn TXT Rust function skeleton
;todo TXT TODO comment
;save KEY Sends Ctrl+Shift+S
;header TXT+KEY Section header with divider
;ip SCR (PowerShell) Insert your public IP
;localip SCR (cmd) Insert your local IPv4 address
;cliplast TXT Paste most recent clip
;clipnr TXT Paste clip by number
,-1c … ,-5c TXT Glue N-th most recent clip

The ;ip sample uses the powershell executor to run (Invoke-WebRequest -Uri 'https://api.ipify.org' -UseBasicParsing).Content. ;localip uses the cmd executor to run ipconfig | findstr IPv4.

What happens to existing triggers

Samples are imported under their shipped keyword. If you have a trigger with the same keyword, the import dialog shows a conflict badge on that row. Your options:

  • Leave the checkbox unchecked — row is skipped, your version stays.
  • Check “Overwrite” next to the conflict — the existing trigger is replaced with the shipped version.
  • Tick the row but leave “Overwrite” off — the row is also skipped (same as unchecked).

The standard Undo entry in the import result covers overwrites, so accidentally replacing a customised trigger can be reverted in one click.

Updating samples

Blue Synergy occasionally tweaks a shipped sample — clean up a body, fix a typo, change an executor. Running Load Sample Triggers… after an update is how you pick up those refreshed versions. The import dialog’s conflict/overwrite flow lets you decide per-sample whether to accept each change.

  • triggers-yaml-import — the standard YAML-import dialog used here
  • triggers-keystroke-tokens — tokens you’ll see in sample TXT bodies ({date}, {cursor}, {clip:last}, …)