ctrl+] won't go forward in journal
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
Research direction
Reproduce the issue from Journals using the upper-right “Go Forward” button and Ctrl+] on Windows 11, checking navigation to a future date without an existing journal entry. Trace the journal navigation entry points and determine the intended behavior for missing future files. Done means both controls advance consistently and the behavior for empty future dates is covered by a regression test.
Written by the indexing model from the issue text.
Description
Search first
- I searched and no similar issues were found
What Happened?
on the current days Journal, clicking the "Go Forward" button, upper right corner, windows 11, won't go forward.
ctrl+] also does not advance.
I'm assuming these actions should create files, in advance of the day, as I cycle through them?
Reproduce the Bug
- click Journals, get brought to "Today"
- click the "Go Forward" button, upper right, or Ctrl+]
- go to tomorrow, or the next journal entry.
- it don't go.....
Expected Behavior
it should go forward.
Should it create a mess of empty files? I assume it might need to?
Maybe just go forward until I type something? That seems wasteful.
If it's Friday, and I just want a note for myself for Sunday, when I look at LogSeq, I just want to easy add that.
I don't think it's reasonable for folks to go forward 100 days by just sitting on the Ctrl+] keys, but you all decide what needs to happen here.
Screenshots
No response
Desktop or Mobile Platform Information
App Version: 1.0.0
Git Revision: 680b371
Platform: Mozilla/5.0 (Windows NT 10.0 Win64 x64) AppleWebKit/537.36 (KHTML like Gecko) LogseqOG/1.0.0 Chrome/140.0.7339.240 Electron/38.4.0 Safari/537.36
Language: en-US
Plugins:
Additional Context
I MIGHT look into submitting a PR for this.
If anyone feels like sending my github email a link to a setup to do development, i'll certainly take a look.
But I'm a 20+ year .NET dev, so I think i'm a total noob for this repo, right?
Are you willing to submit a PR? If you know how to fix the bug.
- I'm willing to submit a PR (Thank you!)
- Dominant language
- Clojure
- Stars
- 316
- Forks
- 56
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from logseq/og
-
Difficulty 4/5 3-5 days Newbie friendliness 62/100
-
Difficulty 3/5 1-2 days Newbie friendliness 76/100
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
.Needs Triage .Team/UXWest Priority:P3 Type:Bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
metabase/metabase#83410 · 1 comment ·
Maintainers usually reply within 1 day
-
contribution welcome good first issue WG adoption
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Setup dependabotOpen
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
software-mansion/starknet-jvm#631 ·