Closed avelino closed 1 year ago
Run into the same issue yesterday. Would be great if the TODO/DONE could be ignored I guess?
A general fix could be to add a syntax in the template like {TODO|DONE}
that would make the plugin match this block no matter if TODO or DONE is present? I'm guessing this could be useful to others with heavily customized setups.
I tried to understand the code to see if I would be able to do the implementation, but I didn't find it so simple to implement the logic
probably the maintainers can do this implementation with more property
sorry for not being able to solve the reported "problem" :(
Hey @avelino @thiswillbeyourgithub , the plugin has been updated to address this issue.
We will only update the article block if there is any property being changed
I like to control in logseq the tasks I need to do, for this I use
TODO
reading is one of the tasks I have in the day and I use the omnivore for capturing and reading (on the laptop)
template that I use in logseq (with TODO):
every time I make an annotation or mark a passage of text and omnivore overwrites the block, making me lose track of what was already done
example:
I marked a task as
DONE
was overwritten: