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 12:17:33 +0100 [thread overview]
Message-ID: <50DED14D.1080402@gmx.de> (raw)
In-Reply-To: <87txr5cftc.fsf_-_@bzg.ath.cx>
On 12/29/2012 11:29 AM, Bastien wrote:
> Hi Simon,
>
> (New thread for this topic.)
>
> Simon Thum<simon.thum@gmx.de> 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
next prev parent reply other threads:[~2012-12-29 11:17 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 ` Simon Thum [this message]
2012-12-29 13:29 ` In agenda, better handling of files changed behind Org's back Bastien
2012-12-29 13:40 ` Simon Thum
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=50DED14D.1080402@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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).