Allow Users to Configure the Conditions Needed for Matches with "word: true" to expand. about espanso HOT 3 CLOSED

I have since found the word_separators option, my apologies.

I have since set the following.
word_separators: [" ", ",", ".", "?", "!", "\r", "\n", "\r\n", "\t", "}", "]", ">", "%", ")", 22]
in my defaults.yml

This allows the use of TAB ⇥ for expanding, however this still results in the erroneous addition of two whitespace after pressing TAB ⇥ unless $|$ is present at the end of the replace: field.

I believe it would be helpful if word_separators would/could be divided into separators for before and after the trigger.

I have since added $|$ to almost all my replace: fields.

PS: What does 22 mean in the word_separators: ?

from espanso.

PS: What does 22 mean in the word_separators: ?

Got curious so I checked. In code it seems to be 22u8 as char:

So - raw ASCII codes in case you want an invisible space seperator or something weird like that ig

from espanso.

Thank you.
Most of your issues are addressed by adjusting the list of word_separators:, as you suggest, and we're in the process of updating the code and documentation to add ", ', \t, and form-feed as defaults. The newline issue is not a problem with the current release.
Regarding item 4, most of us would use a prefix or suffix character or other workaround.
Thank you very much for your suggestion to include closing parentheses - I've added a comment to the pending pull request.
I'll close this for now, if that's OK.

from espanso.