nvim-orgmode / nvim-orgmode/orgmode

Add option to have repeated items/habits stay in the agenda when done

Open
#1,051 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Lua
Stars
3.9k
Forks
190
Avg merge
2d 13h
Merged PRs (30d)
7

Description

Does this feature exist in Emacs orgmode core?

N/A

Orgmode link

No response

Feature value

Touching back on the discussion in #348 and related to the implementation of habits #359 it would be nice to have the option for repeated events (repeaters and habits) not to be taken down from the agenda view.

The use case of this is if you want to see what you did today/last week/last month/last year. Currently, as it is in Emacs once the repeated item is done it's taken out of the Agenda view like so:

Image

Once done:

Image

Looking at your day you would say you did nothing and maybe wonder why you did nothing all day 😄

Also if you want to see how many of the repetitions of an event (say music class) you missed the past month and when you cannot do it in the Agenda now - you have to look at all the repeats for the event.

On the side of habits - say you wanna do some exercise at least every 4 days and at most every 2 days, it would be nice to be able to see all the times you did the exercise in the Agenda view as kind of a tracking thing.

I understand that the current behavior is useful for not crowding the Agenda with many small repeaters/habits, but it would be nice to have an option for them to be there.

Additional context

No response

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

Read related issues #348 and #359 first, then trace the agenda view's handling of completed repeaters and habits. Define how an opt-in setting should retain completed occurrences without crowding the default view, and verify behavior for repeaters, missed repetitions, and habits.

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
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.