From efbdd206fd8d956772da233af42f81617520d977 Mon Sep 17 00:00:00 2001 From: Stefan Wrobel Date: Thu, 24 Sep 2020 11:09:48 -0700 Subject: [PATCH] Note to avoid conflict with macOS text replacement I've tried many different characters, and the only one that I found to work was /, but I'm open to other suggestions for how to document this! --- docs/get-started.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/get-started.md b/docs/get-started.md index dfeb099..84484c9 100644 --- a/docs/get-started.md +++ b/docs/get-started.md @@ -141,6 +141,10 @@ espanso restart Now try to type `:br` anywhere. If you did everything correctly, you should see `Best Regards` appear! +##### macOS remarks + +If are using built-in macOS text replacement (System Preferences > Keyboard > Text - note that these will sync from iDevices if you have iCloud sync enabled), and have any triggers that overlap with espanso (the Replace column in System Preferences), you may find that you get double expansions. Starting your espanso trigger with `/` will prevent macOS text replacement from triggering as well (ex: `/br` instead of `:br`). + #### Quick Editing If you are comfortable using the terminal to edit your configs, you can also use the much quicker: @@ -212,4 +216,4 @@ You can also disable this behavior by adding the following line on your `default undo_backspace: false ``` -> Note that backspace undo is not available for every match, namely the ones that specify a [Cursor Hint](/docs/matches/#cursor-hints) \ No newline at end of file +> Note that backspace undo is not available for every match, namely the ones that specify a [Cursor Hint](/docs/matches/#cursor-hints)