On 8/6/2012 2:16 PM, Allen S. Rout wrote:
One common use would be to store the creation & last-modification dates
of each entry. I've tried various ways of doing it and they all were
too obtrusive to use on _every_ entry. Time-stamping of all entries
would be extremely useful, just as time-stamping of files is.
But I don't want to see the timestamps during normal Org usage.
As a user, if your code is decorating my tree, I want to know it. If
you hide it, I'd be mad. Org is my life in plain text, not WordPerfect
with reveal-codes.
For decorations that change behavior, e.g. export options or inherited
properties, sure.
But meta-information such as creation/modification times or unique node
ids, which do not change behavior and are known to be associated with
every node, displaying them is a distraction. If you already know that
every node has a creation time, what is added by seeing a :PROPERTIES:
line for that node? If anything, it obscures nodes that do have unique
properties you want to know about.
