UPDATE: 2025-02-04
wow, i dont know if this is new or if I stumbled upon something thats been sitting in plain site all along, but today, when after entering a part of a logseq node , with either the # or [[]] notation, if subsequently I type q comma and a space, , then no typesense autocorrection occurs!
The issue
An example that is around undo-ing auto-corrections, when using the Logseq app. This is on on typewise
example
Thoughts as to why
The issue I suppose is that when one types some text, on typewise, a buffer of the immediate text is kept, so if typewise auto-corrects, and someone taps the “↩️” undo , typewise attempts to replace the suggestion with the previous buffer. And if typewise is being used in an app that, say, modifies the text after typewise captures its buffer, but then applies an autocorrect, then of course the undo will not make sense. But say if typewise captures its buffer instead, not right after the last typewise keystroke, but before typewise issues its autocorrect, then everything would be golden.