filenametimestamps for YYYY-MM-DD_blah files about memacs HOT 4 CLOSED

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

:END:

from memacs.

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

from memacs.

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:

• matching mtime and date stamp of file name -> full time stamp in Org
• days not matching (mtime and date stamp of file name) -> date stamp in Org

As awieser wrote: you can now disable this using the --skip-file-time-extraction parameter.

HTH

from memacs.

Thanks guys, just what I was after (and the explanation was as I expected). One step closer to org-mode taking over the universe...

from memacs.