NotePlan
NotePlan
Oct 18

Support - [ ] as default

I would like to have the option of tasks created by default use the '- [ ]' syntax, for ease of working with other tools and people. For example, I am currently collaborating with someone who uses obsidian, and having tasks on our mutual checklist be readable as tasks by his obsidian would be very helpful.
CompletedCompleted

Oct 26, 2023

Supported in Markdown settings when you turn off "Recognize * as Todo" and turn on "Use - as default". Will reopen if I misunderstood the request.

Oct 26, 2023

Eduard Metzger: the way the issue has been described in the OP, it is - strictly speaking - already "completed". But, as I understand it, the reason why people are having problems is that you cannot turn on "recognize `*` as Todo" and at the same time use `- [ ]` as your default for creating new todos (which is what you want e.g. if you have been using `*` for some time and now want to switch to `- [ ]`. BTW: why is `*` the default setting in NP anyway?

Oct 26, 2023

Steen Comer Daniel Danilov Did you try this setting? It seems to do exactly what you say (see attached). New tasks (like hitting enter after an existing task) creates as `- [ ]` for me. Do you see something else?

Oct 27, 2023

Eduard Metzger: I think the misunderstanding here is that we want to keep bring able to create tasks with * task, but have it be rendered as - [ ] regardless. I added more details in the comment below.

Oct 28, 2023

Eduard Metzger: This for me creates a task with `-` as the prefix, not `- [ ]`.

Oct 24, 2023

Yes, please! This has been giving me issues as welll. I remember asking for it in Discord, but that didn't lead anywhere. Thanks for starting a feature request! The same can be said for embedding images via markdown, which works differently in NotePlan than it does in other apps.

Oct 24, 2023

I believe this is already supported.

Oct 25, 2023

Chris: what I want supported is the creation of new tasks with that syntax, not recognizing extant ones.

Oct 26, 2023

Steen Comer: Oh, sorry for the misunderstanding. So, you mean the creation of new task via the ⌘L shortcut? Have you tried this setting

Oct 26, 2023

Upon further testing, I do realize that once you select "Recognize `*` as Todo", the creation of new tasks reverts back to using `*` as default. This seems to be a bug. Eduard Metzger. Even if it is, for some unknown reason, intended, the UI doesn't make sense (why would "recognizing `*` as todo" imply "using `*` as default"?

Oct 26, 2023

Chris: Seems to work for me as expected. Turn off "Recognize * as todo" and default to "-" and I get `- [ ] ` tasks by default. Turning on "Recognize * as todo" makes the default setting below redundant.

Oct 26, 2023

Eduard Metzger: Yes, that is the behaviour I described above. But (apart from the UI not making sense), the problem is that you cannot turn on "recognize `*` as Todo" and at the same time use `- [ ]` as your default for creating new todos.

Oct 26, 2023

Chris: Yes, that's the idea. You want to create todos as `* todo` and as `- [ ] todo`? It seemed to me you don't want to mix that up. Rather use `* ` as bullet and `- [ ]` as todo for example.

Oct 26, 2023

Eduard Metzger: > You want to create todos as * todo and as - [ ] todo? That's not what the UI says. It says "recognize", not "create". One is about how the note should be parsed, the other what should happen when you press ⌘L (for example). It seems perfectly plausible that users might want `*`to be recognized as todo (e.g. for legacy reaons) reasons but use standard markdown for compatibility reasons or whatever.

Oct 27, 2023

I agree with Chris. I understood that setting to mean that when you type out * task, it'll be recognized as a task; however, the markdown format behind the scenes will still remain as - [ ] task. This will make it far more consistent for interoperability. It will also make it easier and more consistent to filter for specific tasks, since we can then use specific status updates in searches. cc Eduard Metzger

Oct 28, 2023

Chris: for me this creates tasks with a prefix of `-`, not `- [ ]`.

Oct 29, 2023

Steen Comer: You need to turn off all "Recognize at" options.

Oct 29, 2023

Daniel Danilov: Definitely could be a feature. This can be a new canny request.

Oct 29, 2023

Chris: Yes, sounds like a new feature request.

Oct 29, 2023

Eduard Metzger: Aha! That worked. In that case, I re-file this as an issue with the text in the settings. I can just barely see the logic of how those settings would lead to this result, but it is, for me, in no way implied.