emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Simon Thum <simon.thum@gmx.de>
To: Bastien <bzg@gnu.org>
Cc: Charles Sebold <Charles.Sebold@lcms.org>, emacs-orgmode@gnu.org
Subject: Re: Possible bug in parsing / clarification of syntax
Date: Mon, 16 Apr 2012 20:38:18 +0200	[thread overview]
Message-ID: <4F8C671A.1090105@gmx.de> (raw)
In-Reply-To: <87aa2j4hoj.fsf@gnu.org>

Hi Bastien,

I have to revoke my earlier statement. The patch does _not_ remove the 
TODO_ line from the agenda. I see no change at all.

Cheers,

Simon

On 04/10/2012 07:31 PM, Bastien wrote:
> Hi Simon,
>
> Simon Thum<simon.thum@gmx.de>  writes:
>
>> I have found some irritating behaviour, potentially a bug. I have a block
>> agenda which goes like:
>>
>> tags-todo "@home&TODO=\"TODO\"
>>
>> and it displays a certain org line that reads
>>
>> **** TODO_ state triggers
>
> Can you try the following patch (against latest hotfix HEAD) and report?
>
> Charles, can you let me know if this breaks anything in your usage of
> `org-map-entries'?
>
> David's original fix want to the right direction, except that we also
> want to match "* TODO" as a headline.
>
> Thanks for testing this quite heavily.
>
>
>
>
>

  parent reply	other threads:[~2012-04-16 18:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-04 21:30 Possible bug in parsing / clarification of syntax Simon Thum
2012-03-18 17:40 ` David Maus
2012-04-10 17:31 ` Bastien
2012-04-15 20:05   ` Simon Thum
2012-04-16 18:38   ` Simon Thum [this message]
2012-05-08 12:13     ` Bastien
2012-05-13 15:38       ` Simon Thum
2012-05-13 16:52         ` Nick Dokos
2012-05-13 17:56           ` Bastien
2012-05-13 18:11             ` Nick Dokos
2012-05-13 17:54         ` Bastien
2012-05-13 18:48           ` Simon Thum
2012-05-14 14:30             ` Sebold, Charles
2012-05-14 15:15               ` Bastien
2012-05-14 14:29           ` Sebold, Charles

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=4F8C671A.1090105@gmx.de \
    --to=simon.thum@gmx.de \
    --cc=Charles.Sebold@lcms.org \
    --cc=bzg@gnu.org \
    --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).