-
Notifications
You must be signed in to change notification settings - Fork 51
feature request: More options for checkmarks #42
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
Comments
This reminds me of callouts, in that it hijacks some standard markdown syntax to do something else. It even hijacks the same thing, a link, which is kind of interesting. Is this supported by any other markdown system, i.e. github flavored markdown? What's happening here is that the non empty block, i.e. While I can see the issue given your particular workflow, I think this falls outside of anything this plugin should support. I'll see if there's some way I can enable you to support this functionality. |
I'm second this request, but I only need
Not for |
# Details Proposed in: #42 Take a similar approach as callouts and use shortcut_links in list items as custom states of a checkbox. Configurable through checkbox -> custom. Each value must provide text, icon, and highlight.
Is your feature request related to a problem? Please describe.
I have been testing the plugin with my lists and encountered a minor annoyance in my workflow. I often use symbols other than "X" in my checkmarks to indicate various statuses such as progress, cancellation, rescheduling, etc.

Describe the solution you'd like
I was wondering if an option could be added to support a couple of other "custom" symbols for concealment.
Describe alternatives you've considered
I found similar functionality in Neorg, but their implementation is a bit wonky and only supports their own markup language.

Alternatively, is it possible to conceal "-" if checkmark box (

- [ ]
) is not empty instead of turning it into a bullet (•)?Additional information
No response
The text was updated successfully, but these errors were encountered: