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 14:40:55 +0100 Message-ID: <50DEF2E7.70609@gmx.de> References: <50BFBD05.4090605@gmx.de> <87licnsun6.fsf@bzg.ath.cx> <50DA0329.6070303@gmx.de> <87txr5cftc.fsf_-_@bzg.ath.cx> <50DED14D.1080402@gmx.de> <87wqw1f0lu.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]:35369) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tower-0001ds-Nn for emacs-orgmode@gnu.org; Sat, 29 Dec 2012 08:41:02 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Toweq-00057M-N0 for emacs-orgmode@gnu.org; Sat, 29 Dec 2012 08:41:01 -0500 Received: from mout.gmx.net ([212.227.15.19]:57171) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Toweq-00056f-Dk for emacs-orgmode@gnu.org; Sat, 29 Dec 2012 08:41:00 -0500 Received: from mailout-de.gmx.net ([10.1.76.20]) by mrigmx.server.lan (mrigmx001) with ESMTP (Nemesis) id 0M4lNL-1SqVug1XYb-00yxQT for ; Sat, 29 Dec 2012 14:40:59 +0100 In-Reply-To: <87wqw1f0lu.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 02:29 PM, Bastien wrote: > Hi Simon, > > Simon Thum writes: > >> 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. > > I understand and I agree. > > There is no simple fix, though. I'll put this on my "watch list". Thanks for that. I assumed it would be easier. I'm using a fair amount of generated org files, and what especially sucks with this behaviour is that _each changed file_ requires one agenda building attempt. So before re-reading 3 org files it is easier to restart emacs. Cheers, Simon