New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question: Tasks are not physically moved (is this expected behavior?) #7
Comments
I started to see the same behaviour since last week (before it was moving the tasks as you expected). Probably related with one of the last logseq updates? |
Same issue for me, hopefully it can be fixed. Will keep an eye on this issue, thanks @luhmann for posting this |
Dito here, seems to have started after update Logseq to the latest version. |
Same here. |
Well, looks like the pull request remains...unfinished business.... I'll show myself out. |
for the quick hack, I fixed it by updating the code directly on the |
@martinkoutecky I've just tried the suggestion from @pararang.
It should work now. |
Thank you for the plugin, which sounds like it would do exactly what I want, but doesn't when I try to use it, so I wanted to ask if I failed to understand correctly or if something is not working as expected.
I added the
unfinishedBusiness
- renderer to my daily-template without a specific tag as decribed in the ReadmeI expected that this would physically move all my non-completed TODOs to the current day.
Instead the TODOs remain on the page before and instead the text "🚀 Moved 4 tasks(by Marker then Priority) from yesterday" is inserted in the current day (see attached screenshot, I would have expected the todos at the bottom to be at the top. I also tested TODOs that are not nested in a block, the result is the same).
Is this the expected behaviour?
The text was updated successfully, but these errors were encountered: