Journal: Friday 2023-11-03 missing and cannot be created

[clayms]

Search first

• [X] I searched and no similar issues were found

What Happened?

For some reason Logseq is refusing to create an entry in the Journal for 2023-11-03 Friday,

When I use the /Tomorrow command on the 2023-11-02 Thursday Journal day, it points to 2023-11-06 Monday. When I use the /Yesterday command on the 2023-11-04 Saturday Journal day, it points to 2023-11-04 Saturday.

Is 2023-11-03 Friday a holiday somewhere that I don't know about?

Using [[2023-11-03 Friday]] will create the entry, but it would be good if /Yesterday or /Tomorrow worked.

Reproduce the Bug

1. Enter /Tomorrow command on the 2023-11-02 Thursday Journal day.
2. Instead, 2023-11-06 Monday is referenced.

Expected Behavior

2023-11-03 Friday should be referenced.

Screenshots

Desktop or Mobile Platform Information

App Version: 0.9.20 OS: Linux x86_64 Git Revision: unknown Platform: Mozilla/5.0 (X11 Linux x86_64) AppleWebKit/537.36 (KHTML like Gecko) Logseq/0.9.20 Chrome/114.0.5735.289 Electron/25.9.3 Safari/537.36 Language: en-US Plugins:

Additional Context

No response

Are you willing to submit a PR? If you know how to fix the bug.

• [ ] I'm willing to submit a PR (Thank you!)

[andelf]

I think this is because /tomorrow and /yesterday is not context-aware.

[andelf]

This should be the expected behavior.

[github-actions[bot]]

Hi There! 👋

We haven't seen any activity on this issue in a while :sleeping:, and we just wanted to make sure that it's still relevant. If you're still experiencing this issue, you might find it helpful to update to the latest version of Logseq. The latest version includes bug fixes and new features that may help to resolve this issue, and you can download it from our website. If updating to the latest version doesn't help, please let us know by adding a comment 💬. We're here to help!

If the issue has been resolved or is no longer relevant, that's great news! 🎉 We'll go ahead and close this issue to keep our backlog organized. Please note that this issue will be closed automatically in 20 days if there is no further activity. If you need more time to resolve the issue or provide more information, please just let us know by adding a comment.

Access additional Logseq 🚀 resources:

• Forum: https://discuss.logseq.com
• Blog: https://blog.logseq.com
• Docs: https://docs.logseq.com

Thanks for your contributions to Logseq! If you have any other issues or feature requests, please don't hesitate to let us know. We always welcome pull requests too!