|
|
|
|
|
by nxobject
483 days ago
|
|
I’m skeptical about convenient plain text is, compared to more structured formats, once we try to encode even more of the conveniences we get out of current calendaring (e.g. time zone shifting, notes of indefinite length, events that last the whole day, repeated events…) There are a few more structured formats for calendaring that share the virtues of their workflows: if we used JSON, would jq be a UNIXy tool? What about sqllite and commandline queries? Both would be much more easier for my overloaded mind - especially when parsing records - without adding more inherent complexity beyond a sufficiently overloaded raw text calendar. |
|