On Friday, February 7, 2020 at 12:00:43 AM UTC-5, Thomas Passin wrote: > > > > On Thursday, February 6, 2020 at 11:04:30 PM UTC-5, andyjim wrote: >> >> attached is my first draft for a zettel format. >> > > Thanks. Here's my first cut at a format. >
Here's a Markdown version of the same thing. You can see that it is basically just a readable, and could be parsed by almost the same parser as the plain text version. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/9c9f1e63-2be6-4e29-867a-3e967416ba4a%40googlegroups.com.
``` title: expermental zettel format 3 id: t-zformat-3 index-term: zettel/format ; this is a comment line ; the "#" has a special meaning in markdown, so we can't use it here. ; order of these keyword entries is not important. ; cite: for citations to published sources ; url: for URLs to relevant web pages. ; rel: for relations to other zettels. parent: t-zformat-2 ; child: id of child zettel. date: 2020/2/5 ; time: 1830 ; Body of note is not introduced by any identifier. ; All data items are optional. format: md ``` This zetel is basically the same as Format 2, except that the keyword lines are formatted as a markdown literal block. **Pros**: Almost as simple to type and parse as Format 1. **Cons**: Have to remember to type the fence characters (if we want it to be formatted by a MarkDown processor). Specific to markdown (could do something similar for RsT). Cannot use the '#' as a comment marker. It might be feasible for a preprocessor to pick md vs RsT by detecting the delineator for the literal block.
