nvim-orgmode / nvim-orgmode/orgmode

Choose the default TODO keyword on new created headlines when you don't want the first keyword

Open
#897 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Describe the bug

If you define the next keywords order because is the one you want it to have in the agendas

        org_todo_keywords = {
          "WAITING(w)",
          "DOING(d)",
          "READY(r)",
          "TODO(t)",
          "INACTIVE(i)",
          "|",
          "DONE(e)",
          "REJECTED(j)",
          "DUPLICATE(u)",
        },

When you create a new headline with org_insert_todo_heading or org_insert_todo_heading_respect_content the TODO keyword will be WAITING instead of TODO.

Steps to reproduce

Create a headline with the scenario described above

Expected behavior

The new created headline has the TODO keyword, or the one the user chooses

Emacs functionality

No response

Minimal init.lua

-- Enter your minimal_init.lua here

Screenshots and recordings

No response

OS / Distro

Linux

Neovim version/commit

0.10.4

Additional context

I implemented a fix for this case in this pr using the org_todo_default_state configuration option

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

Start with the implementations of org_insert_todo_heading and org_insert_todo_heading_respect_content, then inspect the org_todo_default_state configuration mentioned in the issue and the referenced PR 842. Reproduce the custom org_todo_keywords case and verify that creating a headline uses the configured default or the user's chosen keyword without changing agenda ordering.

Written by the indexing model from the issue text.

Assessment

Tech stack
lua
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.