logseq / logseq/og

ctrl+] won't go forward in journal

Open
#45 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Clojure
Stars
297
Forks
52
PR merge metrics
No merged PRs in 30d

Description

### Search first

- [x] 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

1. click Journals, get brought to "Today"
2. click the "Go Forward" button, upper right, or Ctrl+]
3. go to tomorrow, or the next journal entry.
4. 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.

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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

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.

Assessment

Tech stack
clojure
Domain
desktop
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.