After using Autocomplete my trigger “qq” breaks the iOS keyboard word suggestion, because “qq” isn’t part of any word in the languages I write in—that’s why I picked it in the first place.
Is it possible to “reset” the keyboard word prediction after Autocomplete, say, by signaling a word boundary to the keyboard?
Bonus question: If so, could you make that “reset” an action step? Because then an action could use it after Markdown markups like *, [, and [^ which break the work prediction also.
I am thinking of using zero width spaces between the markup and the actual text. That indicates a new word, hence the prediction would work again. But I am not sure how this would affect the Markdown parsing. Before sending the draft to other apps I could easily remove all zero width spaces. But am I missing any issues this workaround would cause in Drafts itself?