From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Griswold Subject: Re: Agenda dispatcher changes files Date: Sat, 31 Jan 2009 13:09:58 -0500 Message-ID: <87r62jibyh.fsf@cantor.griswold.home> References: <87r62jsjrg.fsf@cantor.griswold.home> <0AD25C50-4690-4A94-8911-9F7FDAD1E44B@uva.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LTKI6-0001ix-Qx for emacs-orgmode@gnu.org; Sat, 31 Jan 2009 13:10:02 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LTKI5-0001iV-9i for emacs-orgmode@gnu.org; Sat, 31 Jan 2009 13:10:02 -0500 Received: from [199.232.76.173] (port=37266 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LTKI5-0001iQ-58 for emacs-orgmode@gnu.org; Sat, 31 Jan 2009 13:10:01 -0500 Received: from hrndva-omtalb.mail.rr.com ([71.74.56.125]:39517) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LTKI4-0003TG-S4 for emacs-orgmode@gnu.org; Sat, 31 Jan 2009 13:10:00 -0500 In-Reply-To: <0AD25C50-4690-4A94-8911-9F7FDAD1E44B@uva.nl> (Carsten Dominik's message of "Sat\, 31 Jan 2009 17\:32\:42 +0100") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Carsten Dominik Cc: emacs-orgmode@gnu.org Carsten Dominik writes: > Hi Dan, > > If you want to help, the way to do it is to construct a minimal > example, a testfile with minimal Org customization that can reliably > reproduce this problem. I am sure that I can then easily find the > bug and resolve it. > > - Carsten Thank you, Carsten. Taking your suggestion, I may have narrowed down the problem. I started out using a minimal org file with these contents: * Big item ** MAYBE Subitem ** TODO Another subitem * Another one ** INPROCESS do something SCHEDULED: <2008-01-30 Wed +1w> ** TODO do something else SCHEDULED: <2009-01-31 Sat> Executing C-c a a would NOT mark the file as changed. However, once I added this: #+TAGS: @COMPUTER(c) @PHONE(f) and gave the tag "@COMPUTER:" to the "do something" line, then C-c a a would mark the file as changed. Please let me know if you need more testing, or values for other variables. Cheers, Dan