Hi Achim,
Achim Gratz writes:
> I think that, aside from the above suggestion, it may be worth pondering if
> Org should really "visit" those files that it just needs to look at for
> building the agenda. If it would not visit them (Emacs must visit a file
> that the user opened in edit mode ob
Am 29.12.2012 14:29, schrieb Bastien:
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.
If that is true (I don't really know), then auto-revert-mode should keep
them in sync with the file on disk.
There is no simple fi
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
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, t
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
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 "
