todo functionality
Any plans for future "to do" functionality. A method of ticking or checking off items on a list. Or automating strikethrough of a line similar to Taskpaper.
I know NvAlt stuck with standard plain text and that there are many other apps to handle todo's, but having all my notes and tasks in one app is desirable.
-
Sure! You can do it already -- `[ ] foo` is an undone task, and `[X] bar` is a completed task. Or whatever syntax you prefer...
:)
If you want to automate it, you can use text expansions: http://support.multimarkdown.com/kb/composer-v4/multimarkdown-composer-v4-expansions
As for built-in automated behavior to manage this, then no. That is probably something that will remain out of scope for this project. As you say, there are plenty of apps/utilities to automate some of this and (almost) all can interact with nvUltra simply by editing the same text files.
But I guess anything is theoretically possible....
0 -
Thanks for the reply. For now I have a workflow that circumvents the absence and allows me to stay solely in nvUltra on a Mac and out of any other apps.
If I use Drafts for creation of any Todo's, I run an action with a script that adds the necessary "- [ ] " format to beginning of each line in a draft and sends it to my Dropbox NvAlt folder. From there on iOS 1Writer will convert those to tickable boxes in preview mode and on a Mac I will have to simply add the " x " manually in nvUltra as tasks are completed.
But, mark me down as one who wouldn't mind the optional functionality of ticking a box (or such) in nvUltra.
0 -
I also use 1Writer on IOS which support GitHub flavoured markdown style checkboxes and allows you to check and uncheck the checkboxes in the preview.
For me rendering the checkboxes is a must have feature, and it's something that Marked 2 already supports.
Being able to alter the state of the checkboxes from the preview is a luxury, but definitely a nice to have.
1 -
I liked the behaviour of the `@done`, which would strike-though-ize a line it was appended to.
2 -
I've created an Alfred workflow that provides some Taskpaper and SublimeText Plaintasks like functionality in nvUltra.
You can use snippets and hotkeys to create due dates, mark tasks as completed or cancelled, and create new tasks.
You can edit what a new task looks like ([], [ ], -, *, whatever), and what the cancelled and completed marks are.
You don't get clean up of completed/cancelled tasks. You don't get strikethrough of either either (but I think it would be easy to add and I'm considering it for additional cleanup).
Despite it's limitations, it does implement this in nvUltra today without any additional work on Fletcher or Brett. And it is possibly the lowest friction approach I could find at under an hour of development.
0 -
Excellent!
0 -
I would like to fully support the request for an checkbox functionality in the preview pane!
As pointed out by Arthur in this thread, Marked 2 renders the checked (- [x]) und unchecked (- [ ]) boxes. And I am also one of those spoilt by 1Writer on iOS, which not only lets you check and uncheck the boxes in the preview, but also supports creating todo lists by inserting unchecked boxes after line breaks in lists that already contain checkboxes.
3 -
I would like to endorse this feature request. Could you please also consider the addition of notifications, perhaps something along the lines of nvremind (https://brettterpstra.com/projects/nvremind)? Thanks!
0 -
I mentioned this to Fletcher before, so please ignore, but I think it's time that MultiMarkdown adopt the checkbox UI element. It would essentially make a superset, instead of splitting MMD & GFM.
0 -
Hey, looks like it is not there (end of the May 2020). Any chance to see checkbox syntax in the near future?
1 -
It's not on the immediate road map, no.
0 -
As this is one of the most high voted features, any chance it will get implemented Fletcher Penney?
I also would really love to have it. I use 1Writer on iOS which solves it so beautifully :)
0 -
No chance. He has a fundamental problem with it. When you've created your own standard like MMD, you're not going to abandon it.
Personally, I think Markdown needs to evolve into a more usable state.
> Double `__` should indicate underline
> Single `*` should be unrendered
> Follow `https://squidfunk.github.io/mkdocs-material/reference/` for the complete list of features - many of which are already in MMD. It's the best definition going for what should be Markdown2.The fractioning of the language is not good.
0
Please sign in to leave a comment.
Comments
13 comments