emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Peter Hardy <peter@hardy.dropbear.id.au>
To: emacs-orgmode@gnu.org
Subject: Re: refreshing files for agenda building
Date: Wed, 17 Feb 2021 22:20:40 +1100	[thread overview]
Message-ID: <m2h7mbndo7.fsf@graphite.lan> (raw)
In-Reply-To: <87blcjt77m.fsf@m4x.org>

Alan Schmitt writes:
> I have some files that are changed on disk by an external process, and
> it seems that calling org-agenda does not see the changes until I visit
> the file in emacs. The buffers are loaded and they are auto-reverted,
> but for some reason (some cache somewhere?) their contents are not
> up-to-date with what is produced by org-agenda.
> Is there a command to refresh such files? Should I programatically visit
> them? (And if so, do you have a suggestion as to which command I should
> use, I could not find one?)

I occasionally run in to this as well, using webdav to sync my org
files. Currently using org-revert-all-org-buffers to revert all Org
buffers, followed by org-agenda-redo (bound to r in the agenda view) to
rebuild the agenda.

The help text for org-revert-all-org-buffers describes a workflow for a
set of org files tracked in a VCS, including the
org-save-all-org-buffers function. I've been getting by just being
rigourous about saving files when I modify them, but adopting a similar
workflow sounds like it could be useful.


  reply	other threads:[~2021-02-17 11:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-17  8:43 refreshing files for agenda building Alan Schmitt
2021-02-17 11:20 ` Peter Hardy [this message]
2021-02-17 13:07   ` Alan Schmitt

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=m2h7mbndo7.fsf@graphite.lan \
    --to=peter@hardy.dropbear.id.au \
    --cc=emacs-orgmode@gnu.org \


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