You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Have you searched existing Github issues to see if someone has already requested this feature?
Yes, #87 is the only keyword hit (mentions checklists, but unrelated issue)
Is your feature request related to a problem? Please describe.
Heynote supports checkbox rendering for markdown blocks (- [ ] ...). When using Heynote as a running to-do list mixed with other notes, such as noting many small one-off tasks over time, keeping track of these items gets cumbersome.
Describe the solution you'd like
It would be nice to have a menu or panel that allows us to see a "global checklist" in one place. To continue the scratchpad-like UX spirit, this panel should be hidden under a keyboard shortcut (ctrl+L+I for list? ctrl+B for checkBox?). The panel would show lines across all Markdown blocks that have an (unchecked) checkbox prefix.
The actual UX of the menu is flexible. CLI tools that list checkable items like this (e.g. npm create-vite, Bubble Tea's List) typically will let you navigate with arrow keys and toggle checks with space, but just click-to-jump would be fine too. The main value is being able to quick-reference a running to-do list as I go throughout my day. I suspect without proof that a lot of the logic of the language selector panel could be recycled here.
This wouldn't be robust against cases where people are writing actual markdown documents that contain checkboxes in them for others, I don't think trying to figure out how to deal with that is in-scope -- probably either don't use the feature or move the documents.
Describe alternatives you've considered
I have two workarounds, but I don't think either of them would beat a dedicated solution:
You can ctrl+F for the ^\s*- \[ \] Regex and click through the options. Works well enough when there's a small number of these tasks, not very ergonomic.
You can ensure your checkbox is kept in a single block. Fine, but not fun long-term with a mostly-append-only workflow.
But would be better if we had shortcuts to jump to the start/end of the entire buffer?
Additional context
The text was updated successfully, but these errors were encountered:
I can see how this feature could be useful in certain scenarios. However, it seems highly tailored to a specific use case and may not integrate well with other ways people use Heynote, as you mentioned. For these reasons, I'm going to close this as not planned.
Have you searched existing Github issues to see if someone has already requested this feature?
Yes, #87 is the only keyword hit (mentions checklists, but unrelated issue)
Is your feature request related to a problem? Please describe.
Heynote supports checkbox rendering for markdown blocks (
- [ ] ...
). When using Heynote as a running to-do list mixed with other notes, such as noting many small one-off tasks over time, keeping track of these items gets cumbersome.Describe the solution you'd like
It would be nice to have a menu or panel that allows us to see a "global checklist" in one place. To continue the scratchpad-like UX spirit, this panel should be hidden under a keyboard shortcut (ctrl+L+I for list? ctrl+B for checkBox?). The panel would show lines across all Markdown blocks that have an (unchecked) checkbox prefix.
The actual UX of the menu is flexible. CLI tools that list checkable items like this (e.g. npm create-vite, Bubble Tea's List) typically will let you navigate with arrow keys and toggle checks with space, but just click-to-jump would be fine too. The main value is being able to quick-reference a running to-do list as I go throughout my day. I suspect without proof that a lot of the logic of the language selector panel could be recycled here.
This wouldn't be robust against cases where people are writing actual markdown documents that contain checkboxes in them for others, I don't think trying to figure out how to deal with that is in-scope -- probably either don't use the feature or move the documents.
Describe alternatives you've considered
I have two workarounds, but I don't think either of them would beat a dedicated solution:
^\s*- \[ \]
Regex and click through the options. Works well enough when there's a small number of these tasks, not very ergonomic.Additional context
The text was updated successfully, but these errors were encountered: