Open glicksman opened 1 month ago
Done is not strong because it doesn't get rendered, so the first strong character of your block becomes your text.
We should find a way to make these keywords neutral.
By the way, what extension do you use to have RTL/LTR in your doc? Is it logseq-bidi?
1 -
We should find a way to make these keywords neutral.
Since NOW and LATER are reserved keywords if they appear at the start of the block, can you create a small patch to skip them, when searching for the first Strong Character? Ideally, this will be configurable, so each user can adjust these according to their own workflow.
2 -
By the way, what extension do you use to have RTL/LTR in your doc? Is it logseq-bidi?
Yes, I'm using logseq-bidi version 0.3.0
These keywords are the most annoying thing in Logseq. While I look for a solution, please let me know if you have any suggestions.
See screenshot for illustration.
Ideally, the plugin disregards NOW/LATER when it parses them and doesn't count them as the first strong character.