nvim-orgmode / nvim-orgmode/orgmode
Multiple capture prompts destroy data from all but the most recently opened
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 3.9k
- Forks
- 190
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 7
Description
Describe the bug
If you open multiple task capture prompts the data for all but the most recent one will be lost when saved.
checkhealth
Orgmode ~
- ✅ OK Treesitter grammar installed (version 2.0.0)
- ✅ OK Setup called
- ✅ OK
org_agenda_filesconfigured - ✅ OK
org_default_notes_fileconfigured - ⚠️ WARNING
shellslashis not set. This might cause issues with file paths in links. Setvim.opt.shellslash = truein your configuration
Steps to reproduce
- Open a capture prompt for a task by typing
<Leader>oct - Type something into the header
- Open another capture prompt for a task by typing
<Leader>oct - Type something into the header
- :x to close and write the capture prompt
- :x to close and write the capture prompt
At step 5 the data written in step 3 is added to the org file. At step 6 the data written in step 1 disappears and doesn't appear in the org file.
Expected behavior
The expected behavior is that the data written in both step 1 and step 3 is now in the org file.
Emacs functionality
No response
Minimal init.lua
-- Enter your minimal_init.lua here
Screenshots and recordings
No response
nvim-orgmode version
2b91d9a
OS / Distro
Windows 11
Neovim version/commit
v0.11.3
Additional context
No response
Contributor 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.
Research direction
Start by reproducing the issue with oct in two capture prompts, entering different headers and closing each with :x. Trace the capture prompt save and close handling, then verify that both entries are written to the org file instead of only the most recently opened one.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100