nvim-orgmode / nvim-orgmode/orgmode

Can't clock-out again after undo of clock-out

Open
#1,171 0 comments 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

As the title says.

checkhealth

Orgmode

  • ✅ OK Treesitter grammar installed (version 2.0.4)
  • ✅ OK Setup called
  • ✅ OK org_agenda_files configured
  • ✅ OK org_default_notes_file configured
Steps to reproduce
  1. open a new org file
  2. write a header like * foo
  3. <leader>oxi to clock in
  4. <leader>oxo to clock out
  5. u to undo
  6. <leader>oxo to clock out again, but nothing happens
Expected behavior

the logbook should update to clocked-out state

Emacs functionality

No response

Minimal init.lua
-- default lazy.nvim setup ommited here
return {
  'nvim-orgmode/orgmode',
  config = function()
    require('orgmode').setup()
  end,
}


Screenshots and recordings

No response

nvim-orgmode version

f32a06d

OS / Distro

ubuntu 24.04

Neovim version/commit

v0.11.7

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

Start by reproducing the clock-in, clock-out, undo, and second clock-out sequence using the minimal init.lua and the stated Neovim version. Trace the clocking and undo handling, then verify that the second clock-out updates the logbook to the clocked-out state.

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
Quiet
Clarity
Mostly clear
Newbie friendliness
62/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.