From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2 ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id sBaqKhH+LGBCaQAA0tVLHw (envelope-from ) for ; Wed, 17 Feb 2021 11:29:21 +0000 Received: from aspmx1.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2 with LMTPS id SCt1JhH+LGBweQAAB5/wlQ (envelope-from ) for ; Wed, 17 Feb 2021 11:29:21 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 73AD026924 for ; Wed, 17 Feb 2021 12:29:20 +0100 (CET) Received: from localhost ([::1]:57096 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lCL1C-0000y9-1F for larch@yhetil.org; Wed, 17 Feb 2021 06:29:18 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:41392) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lCL0q-0000xw-04 for emacs-orgmode@gnu.org; Wed, 17 Feb 2021 06:28:56 -0500 Received: from [2401:1801:7801:101:be76:4eff:fe18:40e] (port=38786 helo=mta1.hardy.dropbear.id.au) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lCL0o-00021A-BL for emacs-orgmode@gnu.org; Wed, 17 Feb 2021 06:28:55 -0500 Received: from graphite.lan (unknown [159.196.146.240]) (Authenticated sender: peter) by mta1.hardy.dropbear.id.au (Postfix) with ESMTPSA id DF13CA01E4 for ; Wed, 17 Feb 2021 22:21:39 +1100 (AEDT) References: <87blcjt77m.fsf@m4x.org> User-agent: mu4e 1.4.15; emacs 27.1 From: Peter Hardy To: emacs-orgmode@gnu.org Subject: Re: refreshing files for agenda building In-reply-to: <87blcjt77m.fsf@m4x.org> Date: Wed, 17 Feb 2021 22:20:40 +1100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain X-Host-Lookup-Failed: Reverse DNS lookup failed for 2401:1801:7801:101:be76:4eff:fe18:40e (failed) Received-SPF: pass client-ip=2401:1801:7801:101:be76:4eff:fe18:40e; envelope-from=peter@hardy.dropbear.id.au; helo=mta1.hardy.dropbear.id.au X-Spam_score_int: -2 X-Spam_score: -0.3 X-Spam_bar: / X-Spam_report: (-0.3 / 5.0 requ) BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, RDNS_NONE=0.793, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: peter@hardy.dropbear.id.au Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: "Emacs-orgmode" X-Migadu-Flow: FLOW_IN X-Migadu-Spam-Score: -2.36 Authentication-Results: aspmx1.migadu.com; dkim=none; dmarc=none; spf=pass (aspmx1.migadu.com: domain of emacs-orgmode-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=emacs-orgmode-bounces@gnu.org X-Migadu-Queue-Id: 73AD026924 X-Spam-Score: -2.36 X-Migadu-Scanner: scn1.migadu.com X-TUID: OlYLaSOo+eU2 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. -- Pete