emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@altern.org>
To: Nicolas Richard <theonewiththeevillook@yahoo.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-unmodified asks to revert buffer if file was modified outside emacs
Date: Sat, 23 Feb 2013 11:33:45 +0100	[thread overview]
Message-ID: <87bobb2tn7.fsf@bzg.ath.cx> (raw)
In-Reply-To: <87txqiibjj.fsf@yahoo.fr> (Nicolas Richard's message of "Tue, 15 Jan 2013 18:46:56 +0100")

Hi Nicolas,

"Nicolas Richard" <theonewiththeevillook@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.



  reply	other threads:[~2013-02-23 10:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-15 17:46 org-unmodified asks to revert buffer if file was modified outside emacs Nicolas Richard
2013-02-23 10:33 ` Bastien [this message]
2013-02-23 14:10   ` 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:

  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=87bobb2tn7.fsf@bzg.ath.cx \
    --to=bzg@altern.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=theonewiththeevillook@yahoo.fr \


* 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


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).