From mboxrd@z Thu Jan 1 00:00:00 1970 From: Simon Thum Subject: Re: In agenda, better handling of files changed behind Org's back Date: Sat, 29 Dec 2012 12:17:33 +0100 Message-ID: <50DED14D.1080402@gmx.de> References: <50BFBD05.4090605@gmx.de> <87licnsun6.fsf@bzg.ath.cx> <50DA0329.6070303@gmx.de> <87txr5cftc.fsf_-_@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([208.118.235.92]:48094) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TouQE-00040V-Gs for emacs-orgmode@gnu.org; Sat, 29 Dec 2012 06:17:47 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TouQ6-0005s0-Hz for emacs-orgmode@gnu.org; Sat, 29 Dec 2012 06:17:46 -0500 Received: from mout.gmx.net ([212.227.15.18]:58198) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TouQ6-0005rS-9o for emacs-orgmode@gnu.org; Sat, 29 Dec 2012 06:17:38 -0500 Received: from mailout-de.gmx.net ([10.1.76.34]) by mrigmx.server.lan (mrigmx002) with ESMTP (Nemesis) id 0MP3Jh-1Tj7f6314p-006OKh for ; Sat, 29 Dec 2012 12:17:35 +0100 In-Reply-To: <87txr5cftc.fsf_-_@bzg.ath.cx> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Bastien Cc: emacs-orgmode On 12/29/2012 11:29 AM, Bastien wrote: > Hi Simon, > > (New thread for this topic.) > > Simon Thum writes: > >> I'd also like to use this opportunity to ask about more graceful agenda >> handling of changed files. When someone (not emacs) touches agenda files, >> the agenda code fails horribly. That is even if the file is readonly or has >> the "#+READONLY" header (which seems menaingful only to org-mobile). It >> would be preferable to just reload in this case. ATM, I am queried about >> something related to reloading and the agenda cancels no matter what I >> say. > > I get the gist of what may happen here, but I'd need a reproducible > recipe to know where to put the checks. Sorry to put the burden on > your shoulders, but this would help a lot! It's not a burden at all. This recipe breaks for me: 1 ) invoke agenda 2) > touch some_agenda_file.org 3) invoke agenda again I am asked: some_agenda_file.org changed on disk; really edit the buffer? (y, n, r or C-h) No matter what I answer, the agenda does not show up. Using r, I can get the agenda in a repeat call. My argument is that read-only buffers are not supposed to change on emacs' side, so it would always be OK to re-read them. Cheers, Simon