Autocomplete breaks iOS keyboard word suggestions

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?

What, exactly, do you mean by it “breaks” word suggestions?

Normally, when you start typing you get word suggestions (that are more or less good). After Autocomplete the word suggestion feature treats the Autocomplete trigger as the beginning of a new word. Which it does not know, because no word begins with the trigger. Hence no word suggestion.

I’d be interested in more detail, because I don’t see that at all. Are you saying you use your autocomplete trigger, select something to input, and the next word is not giving you suggestions? Because I don’t see that behavior at all.

Maybe open a ticket with a screen capture video demonstrating what you are seeing, with details on OS version, etc.

I used qq as well.

But when I added Raycast, the suggestion was made to use ;; a pair of semi-colons. I like it.