Closed ajft closed 11 years ago
Addendum, some scanning through the org_archive file that was generated and I've found cases where what I think are similarly named files result in different format org entries:
** <2012-12-05 Wed> 2012-12-05-bashhistory_fafnir :PROPERTIES: :ID: af77fd3c467e3050ddd0c29e3353209cdeabe4b2 :END:
** <2012-12-06 Thu 11:32:47> 2012-12-06-bashhistory_warsaw :PROPERTIES: :ID: 37b0a94ced56ecf6a036bd9173646804a7aa92a5
You just found the undocumented feature that time information is extracted from the file itself.
I have just added a new argument "--skip-file-time-extraction" to avoid that.
regards Armin
To be completely specific and as an addendum to the comment of awieser:
The module looks for the timestamp of the corresponding file (mtime). If its day matches the datestamp of the file name, the time (of mtime) is used for generating the full time stamp in the resulting Org-mode file. If the days do not match, the resuling Org-mode file contains only a date stamp (not a time stamp).
So:
As awieser wrote: you can now disable this using the --skip-file-time-extraction parameter.
HTH
Thanks guys, just what I was after (and the explanation was as I expected). One step closer to org-mode taking over the universe...
I've just started using memacs in a limited capacity, I have a large number of log files generated from other sources whose names are of the form YYYY-MM-DD_hostname.log eg "2013-03-08_zurich_data.log"
I would expect (and prefer) that an org-mode entry for them would be:
<2013-03-08 Fri 09:00:01> 2013-03-08_zurich_data.log
Adrian