dobidi / logseq-bidi

A Logseq plugin for adding bidirectional text support, making knowledge management in both LTR and RTL languages possible
GNU Affero General Public License v3.0
27 stars 1 forks source link

NOW and LATER are considered Strong character (While DONE isn't) #19

Open glicksman opened 1 month ago

glicksman commented 1 month ago

Screenshot 2024-05-07 at 1 09 25

See screenshot for illustration.

Ideally, the plugin disregards NOW/LATER when it parses them and doesn't count them as the first strong character.

ahangarha commented 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?

glicksman commented 1 month ago

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

ahangarha commented 1 month ago

These keywords are the most annoying thing in Logseq. While I look for a solution, please let me know if you have any suggestions.