- #TASKPAPER INSERT SEPARATOR PORTABLE#
- #TASKPAPER INSERT SEPARATOR CODE#
- #TASKPAPER INSERT SEPARATOR ISO#
emacs/org mode is by far and away the best choice. If you want a plain text organizational, compositional and scheduling tool that you can use for the rest of your life and know that 30 years down the line it will be actively supported, developed and you will be able to tweak anything you want. It is like wondering why people go through massive amounts of efforts to bake stuff from scratch when there is a super market and bakery down the street, except it is also like I said a resume. Honestly people wanting to make a hobby project from scratch and then brag about it in a blog post to make themselves look like a more savy programmer/techie (hey, not blaming people, when it is done well it is way better than a resume with bullet points) is primarily the reason they dont use org mode. The format for dates is a subset of ISO-8601, except for the slashed variant (1) that’s there for convenience, and the notation for quarters (2022-Q1).
(Even though it wouldn’t be ambiguous from a purely formal standpoint.) Reason is that a blank or empty line separates item groups from each other, so allowing it to appear within descriptions could create visual ambiguity. So the description text of an item (that can span multiple lines) cannot contain a line that’s all blank. A blank line is defined as “a line that is either empty, or that exclusively consists of blank characters”, and a blank character is defined as “a character from the Unicode Space Separator category (Zs)”. (An item “MUST start at the beginning of a line with a checkbox.”) There can’t be any character before the checkbox. It’s on hold right now – that’s mostly due to practical reasons, because it’s relatively hard to implement in tooling.Īllow me to clarify a few details regarding the spec: Nesting of items is not supported, although the idea has come up. I think it is well put and the first one which checks all the boxes for me. Nothing stops one to simply append it to a time.
But I haven't read anythinf about time zones in the primer. But the person hosting the list should probably be the one defining the time zone. > - timezone is necessary for events happening in specific timezones or across timezones
#TASKPAPER INSERT SEPARATOR PORTABLE#
This is the most portable standard, but extended for human editing.
#TASKPAPER INSERT SEPARATOR ISO#
> - date should support an ISO or other standard date format Details and elaborations can be put in a dedicated directoy and refered to.Īlso, it is a _very bad_ idea to work with invisible lines. > - description supporting blank lines (properly indented) would be useful for longer descriptions The fixed amout of four characters obviously lines up to the start of the text from an item.Īnd is a simple standard for identation rules. > - description indentation limit of four space characters is a problem for nested items Probably that a blank line is used as a separator > - not clear what "item must not contain blank lines" means If your are refering to tabs I don't think this is bad or good. > - specifies a specific space character when a character class would be betterĪSCII has no official character class. Additionally, that can be implemented in your plugin of choice.
If you can tick all items within a nested list, why bother writing it with dedicated TODO items? Additionally, you can just create more files for elaboration.
#TASKPAPER INSERT SEPARATOR CODE#
No benefit in supporting unicode code points. Having a simple ASCII char set helps portability _a lot_. Your plugin can display it with a unicode character.
0 kommentar(er)
