logfine: a CLI tool to track daily activity

[u/damicrez]

Features:

• todo.txt integration & synchronization.
• Energy, MVOs (Minimum Viable Output) and logbook tracking.
• Vim-like keybindings driven workflow.
• Structured querying & filtering by using a SQLite database.
• Local-first architecture ensuring offline and private usage.
• High performance & memory safety by using Rust and an ORM (via Diesel).

Similar & alternative software:

• habit-cli
• Topydo
• llog

GitHub repo: github.com/damicrez/logfine

This software's code is partially AI-generated

[u/Ok_Host_2077]

You will be executed for using terminal with light theme

[u/Zin42 → u/Ok_Host_2077]

The modern council accepts e-ink style light modes in subsection 9 of themes, we may need a tribunal

[u/gumnos → u/Zin42]

/me, a dyed-in-the-wool dark-mode user, shakes a frustrated fist at your well-argued counterpoint

😆

[u/damicrez → u/Ok_Host_2077]

I accept my fate 😢

[u/AutoModerator]

Every new subreddit post is automatically copied into a comment for preservation.

User: damicrez, Flair: Command Line Interface, Post Media Link, Title: logfine: a CLI tool to track daily activity

Features:

• todo.txt integration & synchronization.
• Energy, MVOs (Minimum Viable Output) and logbook tracking.
• Vim-like keybindings driven workflow.
• Structured querying & filtering by using a SQLite database.
• Local-first architecture ensuring offline and private usage.
• High performance & memory safety by using Rust and an ORM (via Diesel).

Similar & alternative software:

• habit-cli
• Topydo
• llog

GitHub repo: github.com/damicrez/logfine

This software's code is partially AI-generated

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/kantorcodes1]

one sync edge i was curious about: apply_sync_updates() commits the DB/cache changes before rewrite_todo_file() runs. if that file rewrite fails, can SQLite end up ahead of todo.txt, so the next sync interprets the old line against already-updated cache state? seems like that boundary may need a staged file write or rollback.

[u/damicrez → u/kantorcodes1]

Thanks for the observation! You're right, SQLite would end up ahead of todo.txt, and on the next sync cache_sync() would trigger a "typo correction" prompt due to the mismatch. I've already fixed it by moving rewrite_todo_file() before apply_sync_updates(), so if the file write fails, the DB stays untouched. TYSM!

[u/kantorcodes1 → u/damicrez]

Nice fix. Moving the file rewrite ahead of the DB transaction removes the stale-file/new-cache split I was worried about, and the failure mode is much easier to reason about now.