epwalsh / epwalsh/pomo.nvim

Persists through Close

Open
#30 0 comments 7 reactions 0 assignees View on GitHub
feature request
Dominant language
Lua
Stars
310
Forks
17
PR merge metrics
No merged PRs in 30d

Description

### 🚀 The feature, motivation and pitch

I am very happy this plugin now exists; however, on occasion I will close nvim and re-open during a "work block" and would like some sort of persisting timer if possible. This could operate with some files managed by the plugin and reading in these files upon nvim startup to see if any active timers are still running or clear files that have expired timers.

### Alternatives

_No response_

### Additional context

_No response_

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue names no files or tests. Start by locating pomo.nvim’s timer creation, shutdown, and startup entry points, then define how active and expired timers are represented across Neovim restarts. Done means an active timer resumes after closing and reopening Neovim, while expired state is cleared.

Written by the indexing model from the issue text.

Assessment

Tech stack
lua
Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.