Hi Nicolas, "Nicolas Richard" <theonewiththeevill...@yahoo.fr> writes:
> Short story is : if you call org-agenda-list and some agenda files have > been modified outside emacs (e.g. by some revision control system), the > command fails if the user choose to revert the file when asked, leaving > a blank agenda in which 'g' does not work. Does it need a fix ? Which > fix ? Good questions. I think it's acceptable to get this warning when an agenda file has been changed outside of Emacs. But having it twice is clearly wrong. The problems lies in `org-agenda-prepare-buffers' which modifies the properties of agenda files. The deeper problem comes from Emacs, as IMHO changing the properties of the buffer should be fine even when the file has been changed outside, because the text properties of the buffer are part of the buffer, not of the file. remove-text-properties, set-text-properties etc. always ask for a confirmation when the underlying file has been changed outside Emacs. So for now I don't know how to fix this in Org. I will ping Emacs developers for the rational behind the current behavior of remove-text-properties and friends. Thanks, -- Bastien
