Snippets feature broken in some applications
I have been using the Snippets feature on and off since it was made available in Beta. Today I started creating a few signature snippets since my team is moving collaboration tools and I want to easily be able to use a specific email signature.
Depending on the application, I have mixed results. This is not an all inclusive list, but highlights the various behavior of the snippet functionality. I have been using this format to keep from accidentally using the string without meaning to use the snippet ( ::shortcut:: ) but in the below examples I have left off the colons so I don’t convert to the expanded text.
- Front (email client): Snippet works as expected
- Slack: Snippet shortcut disappears, no text is entered, but I hear the Snippet sound effect, as if it converted the shortcut to the expanded text
- Apple Notes: Snippet works as expected
- TextEdit: Snippets work as expected
- Things3: The leading and trailing colons (
::shortcut::) do not properly expand the text, but are instead converted to highlighted text, based on their markdown -- this is a me problem -- but even with the other snippet formats, the same affect occurs as slack. No text is entered, but I hear the Snippet sound effect, as if it converted the shortcut to the expanded text
The snippet shortcut ::signature_full:: didn’t work, even when written as signature_full without any leading or trailing special characters. Seems there is a bug that is blocking this.
OS: macOS 26.5.2 (25F84)
App Version: 1Password for Mac 8.12.12 (81212044)