-
Notifications
You must be signed in to change notification settings - Fork 58
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
[Feature Request] Bullets for TODOs #14
Comments
Possible characters can be:
Users can be provided options to use other symbols, such as smileys etc. Still, this is all hypothetical, as I don't know if this can (and will be) implemented or not. |
There is an alternative way to achieve something similar. If you define your toto keyword sequences so that they include a leading UTF8 charcter, you can get similar look. i.e.
The limitation of this is that it isn't backwards compatible i.e. old todo sequences won't work and I don't know what impact this might have on export backends. |
Here's another workaround that preserves existing text while allowing for unicode checklists in org mode: (font-lock-add-keywords 'org-mode
'(("\\(?:\\(?:- \\)?\\[ ]\\)"
(0 (prog1 () (compose-region
(match-beginning 0)
(match-end 0) "☐"))))))
(font-lock-add-keywords 'org-mode
'(("\\(?:\\(?:- \\)?\\[X]\\)"
(0 (prog1 () (compose-region
(match-beginning 0)
(match-end 0) "☑"))))))
;; From http://www.howardism.org/Technical/Emacs/orgmode-wordprocessor.html
(font-lock-add-keywords 'org-mode
'(("^ +\\([-*]\\) "
(0 (prog1 () (compose-region (match-beginning 1)
(match-end 1)
"•")))))) It might be worth building this into |
@msanders it seems like the following fork takes pull requests and is also the one that is used on melpa: |
I want to suggest something like this:
Suppose we have ('*' represents unicode bullet from this package):
Now, setting a
TODO
on a heading should result in:The text was updated successfully, but these errors were encountered: