-
-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tri-state checkboxes #32
Comments
Sounds interesting, do you've any idea how this could look like, I mean syntactically? |
I looked into your code and I'm afraid that this is probably not the easiest thing to achieve because of the fundamental changes it would mean. Instead of just toggling between checked/True and unchecked/False a third state would be needed. Without knowing the extension code in detail I guess that the necessary changes would be anywhere, from the model in |
Regardless of the code I mean how the third state should be displayed in markdown. Maybe we could introduce a "-" inside the brackets to mark it as partially checked, like an intermediate state of the checkbox: - [-] this point is unconsidered yet |
In the manual "pencil and a sheet of paper" world I would probably just skip a checkbox to leave it unsonsidered. I would accept items by "tick-check" and reject items by "x-check". In the current release, "x-checks" in the markdown code are rendered to "tick-checks" in my markdown preview. So obviously my manual habits are not working very well here ;-) I think "-" sounds good to mark an item as unconsidered. With the advantage of leaving the current meaning of "unchecked" as "undone" which is perfect for todo lists. |
I'm also interested in multiple states for checkboxes. Dendron uses different characters inside the brackets. So they have states like "dropped" which is Personally, I'm also interested in finding an extension which supports alternatives to the square brackets. I'd like to be able to track repeating checklists as @PKief Would adding these esoteric cases be a bit over the top for your plugin? |
@chmac adding But the question of using a different markdown syntax |
I really enjoy using this extension, not only for simple to-do lists but also for "decision" lists. I start these lists by enumerating all the options I have and then I consider every single option in detail. What I now miss sometimes is a third state to distinguish between "unconsidered yet" and "rejected". I fully understand if this was not your intention, but maybe a third state is valuable in other use cases as well :-)
The text was updated successfully, but these errors were encountered: