emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Simon Thum <simon.thum@gmx.de>
To: Bastien <bzg@altern.org>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: In agenda, better handling of files changed behind Org's back
Date: Sat, 29 Dec 2012 14:40:55 +0100	[thread overview]
Message-ID: <50DEF2E7.70609@gmx.de> (raw)
In-Reply-To: <87wqw1f0lu.fsf@bzg.ath.cx>

On 12/29/2012 02:29 PM, Bastien wrote:
> Hi Simon,
>
> Simon Thum<simon.thum@gmx.de>  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

next prev parent reply	other threads:[~2012-12-29 13:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-05 21:30 Agenda highlighting bug Simon Thum
2012-12-24  8:48 ` Bastien
2012-12-25 19:48   ` Simon Thum
2012-12-29 10:28     ` Bastien
2012-12-29 10:29     ` In agenda, better handling of files changed behind Org's back (was: Agenda highlighting bug) Bastien
2012-12-29 11:17       ` In agenda, better handling of files changed behind Org's back Simon Thum
2012-12-29 13:29         ` Bastien
2012-12-29 13:40           ` Simon Thum [this message]
2012-12-29 15:47           ` Achim Gratz
2012-12-29 17:50             ` Bastien

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=50DEF2E7.70609@gmx.de \
    --to=simon.thum@gmx.de \
    --cc=bzg@altern.org \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).