Stephen Meech

Unless extending image-matching capabilities is planned, I think we can probably close this as `html:` and `markdown:` mechanisms can now inject images and use {{variables}}.

According to [DeepWiki](https://deepwiki.com/search/espanso-variable-naming-doesnt_0313ef04-2416-4311-b0c1-9ef6aeae0531) this is an Espanso, rather than a YAML restriction. Extending the range may be possible.

Testing suggests, `global_vars:` variables don't get expressed as environment variables (just those within trigger snippets) unless you add e.g. `depends_on: ["clipb"]` to the trigger to force their evaluation first. There's...

[DeepWiki](https://deepwiki.com/search/write-me-a-privacy-statement-f_9fd61c82-85f6-4735-bfc5-0ed71c040e0a) concurs.

The Hub frontend does use Cloudflare analytics tracking, according to [DeepWiki](https://deepwiki.com/search/are-there-any-privacy-or-secur_98149563-669a-4295-bd4c-9e79a743e626), which also suggests Google can track users across sites that use their font service.

Possibly https://github.com/espanso/espanso/discussions/1213, https://github.com/espanso/espanso/discussions/1171#discussioncomment-3068909 I think this is a good idea. A simpler implementation might be to have a key/value pair defining a trigger string at the beginning of a file,...

A global setting would be more complicated because of the number of packages (including all the spell-check and typo-fixer ones) that don't use prefixes at all, but I suppose one...

I think so, although it won't be useful for those who use different prefixes to differentiate between triggers.

Just to be clear - in my mind, there are two ideas: 1. A per-file setting that prefixes _all_ contained triggers with a specified character - those triggers therefore won't...

MInd you, if we encouraged colons as the usual prefix for packages, none of this would be necessary. Users could choose another character for their own expansions.