emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <dominik@science.uva.nl>
To: Dan Griswold <dgriswol@rochester.rr.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Agenda dispatcher changes files
Date: Sat, 31 Jan 2009 22:37:14 +0100	[thread overview]
Message-ID: <14D834F5-FB26-49C7-A4B3-A75C81189046@uva.nl> (raw)
In-Reply-To: <87r62jibyh.fsf@cantor.griswold.home>

Hi Dan,

I can not yet reproduce this, so I need your full customization - or
even better a minimal customization, where you have started Emacs with

emacs -q -l minimal.emacs

Thanks for your help!

- Carsten

On Jan 31, 2009, at 7:09 PM, Dan Griswold wrote:

> Carsten Dominik <dominik@science.uva.nl> 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

  reply	other threads:[~2009-01-31 21:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-31 13:11 Agenda dispatcher changes files Dan Griswold
2009-01-31 16:32 ` Carsten Dominik
2009-01-31 18:09   ` Dan Griswold
2009-01-31 21:37     ` Carsten Dominik [this message]
2009-02-01 11:33 ` Carsten Dominik

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  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=14D834F5-FB26-49C7-A4B3-A75C81189046@uva.nl \
    --to=dominik@science.uva.nl \
    --cc=dgriswol@rochester.rr.com \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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