Naming Your Abbreviations So You Remember Them
Most people who give up on text expansion do so because they cannot remember their own triggers, or because the triggers fire in the middle of ordinary words. A naming scheme fixes both.
Two ways a trigger fails
A trigger fails when you cannot recall it, and it fails when it goes off by accident. The first is a memory problem and the second is a collision problem. A good naming scheme has to solve both at once, and the two pull in opposite directions: short, natural triggers are memorable but collide with real words; long, strange ones never collide and are impossible to remember.
Use a prefix character
The most common solution is to begin every trigger with a character that never starts a normal word: a semicolon, a comma, a slash or a doubled letter. ;em for an email address will not appear in ordinary writing, while plain em appears inside "them", "email" and "remember". Pick one prefix and use it for everything, so your hands learn a single gesture.
Build names from a pattern
- Category then item. ;adhome and ;adwork for two addresses; ;sigf and ;sigs for a formal and a short signature.
- First letters of the phrase. ;lmk for "let me know if you have any questions". Easy to derive when you have forgotten it.
- The word you would search for. If you think of a reply as "the refund one", call it ;refund, not ;r7.
The test of a pattern is whether you could guess a trigger you have forgotten. If guessing works, the scheme is doing its job.
Length
Very short triggers save the most keystrokes and are the hardest to tell apart. A prefix plus a few meaningful letters is a comfortable middle. Saving a hundred characters with five keystrokes is already a bargain; shaving the trigger down to two is not worth the confusion.
Decide how triggers fire
Tools differ. Some expand the moment the last character is typed. Others wait for a space, a punctuation mark or the Tab key. Immediate expansion is quicker and means no trigger can be the beginning of another: if ;ad fires instantly, you will never reach ;adhome. Waiting for a delimiter avoids that problem and costs one keystroke. Know which mode you are in before you name anything.
Keep a visible list at first
For the first few weeks, keep your list somewhere you can glance at it: a sticky note, a pinned document. Looking is not cheating. Most people find the list becomes unnecessary for everyday triggers quite quickly, while the rare ones never stick. That is useful information: an abbreviation you never remember is probably one you do not need.
Prune regularly
Once a month, read through the list. Delete anything you have not used. Rename anything you keep getting wrong; the name you keep typing by mistake is the name it should have had. A library is healthy when it is small enough to read in a couple of minutes.
Sharing with a team
Shared libraries need stricter rules than personal ones. Agree the prefix and the category names before anyone adds entries, name one person to approve changes, and keep personal experiments in a separate group so they do not surprise colleagues.