emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Alan Schmitt <alan.schmitt@polytechnique.org>
To: "emacs-orgmode" <emacs-orgmode@gnu.org>
Subject: refreshing files for agenda building
Date: Wed, 17 Feb 2021 09:43:41 +0100	[thread overview]
Message-ID: <87blcjt77m.fsf@m4x.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 525 bytes --]


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



[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 528 bytes --]

             reply	other threads:[~2021-02-17  8:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-17  8:43 Alan Schmitt [this message]
2021-02-17 11:20 ` refreshing files for agenda building Peter Hardy
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=87blcjt77m.fsf@m4x.org \
    --to=alan.schmitt@polytechnique.org \
    --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).