How to name triggers that are memorable and never collide
A simple naming system for triggers: one prefix, short stems, and no accidental matches while you type normal text.
Denna sida har maskinöversatts från engelska. De engelska och koreanska texterna är auktoritativa.
A trigger is only useful if you can remember it without thinking and if it never fires by accident. With three or four snippets this is easy. With forty it becomes the difference between a tool you trust and one you avoid. Here is a naming system that stays manageable.
Use one prefix for every trigger
The most common cause of accidental expansion is a trigger that is also a real word or a common letter combination. If you name a snippet "ty" you will eventually type it inside another word. Starting every trigger with the same symbol, such as a slash, makes triggers visually distinct and nearly impossible to type by accident. You also build a habit: slash means snippet.
Pick one prefix and keep it. Mixing a slash for some snippets, a semicolon for others and no prefix for the rest means you have to remember the rule for each one, which defeats the purpose.
Short stems, predictable meaning
Aim for three to six characters after the prefix. Anything shorter is cryptic, anything longer you may as well type. Base the stem on the first letters of the key word, not on an abbreviation only you understand. /ship is better than /sh1 because you will guess it on a bad day.
- Use the first word of what the snippet says: /thanks, /hours, /sorry.
- Use a noun for the content, not a verb for the action: /addr instead of /giveaddress.
- Avoid digits as the only difference between two triggers; /q1 and /q2 are easy to mix up.
- Keep to lowercase letters, so you never wonder whether capitals matter.
Prevent collisions with a family system
When you have several snippets about the same topic, give them a shared stem and a short suffix. All shipping answers start with /ship, all billing answers with /bill. Then the family is easy to find, and when you start typing you naturally narrow down.
Your order [Order no.] has been handed to the carrier on [Date]. You can expect delivery within [3-5] business days.
We are sorry, your order [Order no.] is delayed. The new expected shipping date is [Date]. We will update you as soon as it leaves our warehouse.
Your invoice [Invoice no.] for [Amount] is due on [Date]. The payment details are on the invoice.
Notice that /ship is also the beginning of /shipd. If a trigger is the beginning of another trigger, you can run into the situation where the shorter one fires first. To be safe, make the stems different enough that no trigger is a prefix of another: /ship and /shipd could become /ship and /delay, for example.
Check for collisions before you save
Before saving a new snippet, scan the list on the website for triggers that start with the same letters. If one already exists, either rename the new one or reorganize the family. This takes ten seconds and prevents the one irritating moment where a snippet expands when you did not mean it.
Document your system in one snippet
A surprisingly useful habit is to keep one snippet that lists your own prefixes and families, for example /help containing "ship = shipping, bill = billing, hr = hiring". Open it when you forget. If you work with other people, the same list makes handover easy.
Practical tip: say the trigger out loud when you create it. If you cannot say it naturally in one breath, it will be hard to recall under pressure. Rename it now rather than fighting it for months.