Choosing a trigger prefix: how to avoid accidental expansion

The prefix is the character that tells Pine Shortcut you are typing a trigger. Pick one that fits your habits and never clashes with normal writing.

This page has been machine translated from English இந்த பக்கம் machine translated ஆகும். The English and Korean texts are authoritative.அமெரிக்க மற்றும் கிழக்கு மொழிகளில் எழுதப்படுகின்றன.

Every trigger begins with a prefix, a small marker that says: what follows is a snippet name, not ordinary writing. The default prefix in Pine Shortcut is the slash, so /hi followed by Space expands a snippet named hi. For many people the default is perfect. For others, a different prefix saves annoyance. This article helps you decide.

What the prefix is for

Without a prefix, the program would have to treat every word you type as a possible trigger. If you saved a snippet called "btw" and also write the word "btw" in a sentence, you would get an expansion you did not want. The prefix removes this ambiguity. Since / almost never begins a word in normal prose, anything that starts with it is almost certainly a trigger.

What makes a good prefix

• Rare at the start of words. Letters and common punctuation such as the full stop are poor choices.
• Easy to type with one hand, without moving much, on your keyboard layout.
• Not used by the programs you work in for something else.
• Short. Pine Shortcut accepts up to three characters without spaces, but one is usually best.

The position on the keyboard matters more than people expect. On a US layout the slash sits next to the right Shift key and is easy to reach. On other layouts it may require Shift or AltGr, which makes it slower and more error-prone. Test it by typing /hi ten times in a row.

Where the slash collides

The slash is excellent, but it is not perfect. Some programs use it deliberately. Chat tools such as Slack and Discord treat a slash at the start of a message as a command. Web addresses and file paths contain slashes, so typing a path directly after a trigger can look odd. Command lines use it for options.

If you notice the slash clashing in your chat tool, choose another prefix. Common alternatives include the semicolon, the backslash, the double semicolon and the at sign. Test the character in the programs you use daily before you commit.

This line proves that the prefix and trigger work in this program.

Options compared

• Slash (/): the default; quick on US layouts; clashes with chat commands.
• Semicolon (;): easy to reach on the home row; can appear in code and sentences, so keep triggers distinctive.
• Two characters, such as ;; or //: very rare in normal text, a few more keystrokes.
• No prefix: the fastest to type, but triggers must be at least 3 letters to avoid accidental expansion, and they must not look like ordinary words.

Using a different prefix for some snippets

A single snippet can have its own prefix. This is useful when most of your snippets use the slash but one group, for example the snippets for your chat tool, needs a different one. You can also choose a different prefix for snippets in another language, so that the Korean ones always begin with a special character and the English ones with a slash.

Do not create too many variations. Two prefixes are easy to remember; five turn into guesswork. When in doubt, keep one prefix for everything and give the triggers themselves a good structure.

Changing your prefix

You can change the prefix in your account settings. Changing it does not alter your snippets or their names; only the character you type to start them changes. Remember to tell the colleagues who share your wording conventions, and update any notes where you wrote down your triggers. After changing, spend a few minutes using the new prefix on purpose until your fingers learn it.

Thank you for your time today. I will send the summary by this evening.

Think also about how your typing rhythm works. Some people type the trigger in a quick burst: prefix, three letters, Space. For them a two-character prefix feels like a stumble and a single character feels natural. Others pause before every trigger and do not mind a longer start. There is no correct answer; pay attention to which one your hands accept without protest after a few days.

A simple recommendation

Start with the default slash for one week. If you notice problems, such as accidental expansions or clashes with a chat tool, change to a double character or the semicolon. If you never see a problem, leave it. The best prefix is the one you stop noticing. Pair it with short, memorable trigger names, and your snippets will feel like part of the keyboard.