nvim-orgmode / nvim-orgmode/orgmode

Add proper habit support (STYLE: habit) like Emacs Org-mode core

Open
#1,044 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?

Yes

Orgmode link
Feature description

nvim-orgmode has basic support for repeating tasks with SCHEDULED: <YYYY-MM-DD +1d> and :STYLE: habit, but it’s missing the full habit tracking from Emacs Org-mode. Right now:

  • When I mark a habit DONE, it instantly resets to TODO or HABIT and stays in today’s Agenda, even though :LAST_REPEAT: updates.
  • No way to hide completed habits from today’s Agenda (Emacs does this with :LAST_REPEAT:).
  • No streak graphs or proper habit tracking like in Emacs.

This makes daily habits feel clunky — I can’t just mark them done for today without tweaking SCHEDULED manually.

Is this Emacs core?

Yes, habits are core in Org-mode via org-habit.el, which comes bundled and is enabled by default (see Org Manual: Tracking your habits). It’s not a separate plugin

Use case

For a daily habit like:

* HABIT Leetcode
  SCHEDULED: <2025-10-08 Wed +1d>
  :PROPERTIES:
  :STYLE: habit
  :END:

I want:

  • Mark DONE → it’s gone from today’s Agenda, resets for tomorrow.
  • See a simple streak graph (like Emacs’ ASCII bars).

Right now, it resets to TODO/HABIT and stays in Agenda, which breaks the flow.

Environment
  • nvim-orgmode: 03777ca
  • Neovim: v0.11.0
  • Config:
    require('orgmode').setup({
      org_todo_keywords = {'TODO(t)', 'HABIT(h)', '|', 'DONE(d)'},
      org_todo_repeat_to_state = 'HABIT',
    })
    
Feature value

No response

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

No implementation files, tests, or entry points are named. Start by reading the existing habit repeat and Agenda handling, then compare its behavior with the linked Emacs Org-mode habit documentation. Done means completed habits leave today's Agenda, repeat for the next period, and provide the requested streak visualization.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.