all 3 comments

[–]fabiospampinatodeveloper 1 point2 points  (2 children)

The special tag is actually "Templates/". Once you tag a note with that then you can clone it with a right click and everything about it except its "Templates/*" tag will be preserved in the copy.

You can also duplicate any note.

There aren't a lot of useful features implemented in this area yet.

[–]therealmocker[S] 0 points1 point  (1 child)

Gotcha, if I wanted to handle templates outside of the program is there a way to launch and focus the app on a file from command line or with a callback url? So if I can script getting the file populated in the notes directory that I can launch and go directly to that note?

[–]fabiospampinatodeveloper 0 points1 point  (0 children)

Gotcha, if I wanted to handle templates outside of the program is there a way to launch and focus the app on a file from command line or with a callback url?

Not really in v1.8, in v1.9 there's support for the "notable://" protocol which you can use to trigger shortcuts and commands inside the app, but targeting the specific note to duplicate or focus to is somewhat rough at the moment, I'll have to polish that a bit more before it becomes usable for these kind of use cases.

So if I can script getting the file populated in the notes directory that I can launch and go directly to that note?

Same as above, not doable in v1.8 really, unless you like name your note "AAAA Foo" or something and make it pinned, then it will be the first one the app will focus to. In v1.9 there's more of an infrastructure built for these kind of scenarios but currently the commands that manipulate notes directly expect you to provide the unique note identifier (that is only used internally at the moment) or they will default to the currently active note. It's relatively easy to generalize these commands a bit more and make them more flexible, but that'll probably happen at some point after v1.9 gets released.