What
lua/config/orgview.lua renders - [ ] / - [x] checkbox syntax as styled todo/done icons via extmarks (see icons.todo, icons.done, and the bullet branch in render()), but this is purely cosmetic — there is no keymap or command anywhere in the file (or elsewhere in the config) that actually flips a checkbox's state. Real org-mode's <C-c><C-c> cycling has no equivalent here.
Where
lua/config/orgview.lua — render() / icons.todo / icons.done, matches the %[[ xX]%] pattern for display only, no write-back path
Why it matters
The orgview filetype currently looks interactive (styled checkboxes) but isn't — toggling state still requires manually editing the raw [ ]/[x] text underneath the extmark, which defeats the purpose of the styled rendering. Nothing in the existing open [idea] issues mentions org-mode, checkboxes, or task-state toggling.
Recommended action
Add a command/keymap (e.g. <leader>ox or similar, scoped to orgview filetype) that locates the [ ]/[X] span under the cursor or on the current line — reusing the same %[[ xX]%] pattern the renderer already matches — and toggles the literal underlying text between the two states, letting the existing render() extmark logic pick up the change on next redraw.
What
lua/config/orgview.luarenders- [ ]/- [x]checkbox syntax as styled todo/done icons via extmarks (seeicons.todo,icons.done, and thebulletbranch inrender()), but this is purely cosmetic — there is no keymap or command anywhere in the file (or elsewhere in the config) that actually flips a checkbox's state. Real org-mode's<C-c><C-c>cycling has no equivalent here.Where
lua/config/orgview.lua—render()/icons.todo/icons.done, matches the%[[ xX]%]pattern for display only, no write-back pathWhy it matters
The
orgviewfiletype currently looks interactive (styled checkboxes) but isn't — toggling state still requires manually editing the raw[ ]/[x]text underneath the extmark, which defeats the purpose of the styled rendering. Nothing in the existing open[idea]issues mentions org-mode, checkboxes, or task-state toggling.Recommended action
Add a command/keymap (e.g.
<leader>oxor similar, scoped toorgviewfiletype) that locates the[ ]/[X]span under the cursor or on the current line — reusing the same%[[ xX]%]pattern the renderer already matches — and toggles the literal underlying text between the two states, letting the existingrender()extmark logic pick up the change on next redraw.