On 21.3.2012, at 17:32, Karl Voit wrote: > Hi! > > * Nick Dokos <nicholas.do...@hp.com> wrote: >> >> Check that you picked up Carsten's fix (commit ): >> git show 7d84b300f4cba8b726662113d4ce4ff40a76c5b5 > > I do. I did a «git pull» and the «git show» from above shows me > Casten's fix. > >> If you did M-x org-reload RET only, then that's probably the reason: >> check to see if the value of org-ts-regexp0 has been updated; in my case >> it hadn't and I ended up doing M-x load-file RET /path/to/org.el RET. >> Alternatively, restart emacs. > > Being very unsure what needs to be restarted at such updates,
The reason why just reloading a file does not work here is that the regexp is defined as a constant (defconst), which will not be changed on executing the defconst again. So exiting and restarting Emacs is the right thing to do. - Carsten > I > quit Emacs before the git commands and start it again afterwards. > > So I quit Emacs again, did another «git pull» a couple of minutes > ago, compiled all *.el once again, started Emacs, generated the ICS > file and now the times get written to ICS: > > ,----[ Org-mode entries ] > | ** <2012-03-21 08:12> TSTest > | :PROPERTIES: > | :CREATED: [2012-03-20 Tue 10:38] > | :END: > | > | ** <2012-03-21 08:07-13:12> TSTest > | :PROPERTIES: > | :CREATED: [2012-03-20 Tue 10:40] > | :END: > `---- > > ,----[ ICS entries ] > | BEGIN:VEVENT > | UID: TS-4ae514e8-210c-408b-bb08-254dcb3a5277 > | DTSTART:20120321T081200 > | DTEND:20120321T101200 > | SUMMARY: TSTest > | CATEGORIES:misc > | END:VEVENT > | BEGIN:VEVENT > | UID: TS-cab4b928-1960-4335-b2e8-2179e66eec5a > | DTSTART:20120321T080700 > | DTEND:20120321T131200 > | SUMMARY: TSTest > | CATEGORIES:misc > | END:VEVENT > `---- > > ICS look great! Thank you guys for tracing the problem and fixing > it! I really appreciate the help! > > > So far, Google calendar does not use the time information of those > two test entries :-( > > But since the ICS data seems to be OK there might be another hiccup > by Google this time. I created new test entries with different names > and wait for Google calendar to re-read the new data. > > I am optimistic that this is just a caching problem of Google > because I did not change the descriptions during my last test. > > -- > Karl Voit > >