Add option to have repeated items/habits stay in the agenda when done
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 32/100
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.
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:
Once done:
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
- Dominant language
- Lua
- Stars
- 3.9k
- Forks
- 192
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 12
Getting set up
- No 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 nvim-orgmode/orgmode
-
Difficulty 1/5 Under an hour Newbie friendliness 73/100
nvim-orgmode/orgmode#1193 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
nvim-orgmode/orgmode#1175 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 92/100
nvim-orgmode/orgmode#1173 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 50/100
nvim-orgmode/orgmode#1172 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 52/100
nvim-orgmode/orgmode#1170 ·
Maintainers usually reply within 1 day
All issues in nvim-orgmode/orgmode
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
orbitalquark/scintillua#223 ·
-
bug code-annotation
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
quarto-dev/quarto-cli#15215 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
RLS-Modding/rls_career_overhaul#511 · 1 reaction ·
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
P-47D: GEAR_LVR always reads 1Possibly taken @cbass2404 claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 88/100
DCS-Skunkworks/dcs-bios#1932 ·