contrapunctus
/
chronometrist
Archived
1
3
Fork 0
Code Issues 1 Pull Requests Projects Releases Wiki Activity

Tweak term definition

This commit is contained in:
contrapunctus 2022-02-20 01:07:30 +05:30
parent 4c3f220f43
commit 73477552cc
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
elisp/chronometrist.org
View File

@ -49,8 +49,8 @@ Quite recently, after around two years of Chronometrist developement and use, I
:DESCRIPTION: Explanation of some terms used later
:END:
Chronometrist deals with two entities -
+ time intervals (earlier called "events") :: these are currently represented as plists. Each plist contains at least a =:name "<name>"=, a =:start "<iso-timestamp>"=, and (except in case of an ongoing task) a =:stop "<iso-timestamp>"=. Optionally, it may contain other keys.
+ record :: associating a date with time intervals (and possibly key-values). These are currently represented as lists in the form =("<date>" [<keyword> <value>]* <interval plist>+)=.
+ intervals (earlier called "events") :: a continuous range of time spent on a task. These are currently represented as plists. Each plist contains at least a =:name "<name>"=, a =:start "<iso-timestamp>"=, and (except in case of an ongoing task) a =:stop "<iso-timestamp>"=. Optionally, it may contain other keys.
+ records :: these associate a date with time intervals (and possibly key-values). These are currently represented as lists in the form =("<ISO-8601 date>" [<keyword> <value>]* <interval>+)=.
Some other terms
+ row :: a row of a table in a =tabulated-list-mode= buffer; an element of =tabulated-list-entries=.