emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Bastien <bzg@gnu.org>
To: Simon Thum <simon.thum@gmx.de>
Cc: Charles Sebold <Charles.Sebold@lcms.org>, emacs-orgmode@gnu.org
Subject: Re: Possible bug in parsing / clarification of syntax
Date: Tue, 10 Apr 2012 19:31:40 +0200	[thread overview]
Message-ID: <87aa2j4hoj.fsf@gnu.org> (raw)
In-Reply-To: <4F53DEF7.8080604@gmx.de> (Simon Thum's message of "Sun, 04 Mar 2012 22:30:31 +0100")

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

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.


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: fix-mismatched-todo-entries.patch --]
[-- Type: text/x-patch, Size: 512 bytes --]

diff --git a/lisp/org.el b/lisp/org.el
index 3dd8f88..ea5ef7c 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -12824,7 +12824,7 @@ headlines matching this string."
 		     " *\\(\\<\\("
 		     (mapconcat 'regexp-quote org-todo-keywords-1 "\\|")
 		     (org-re
-		      "\\>\\)\\)? *\\(.*?\\)\\(:[[:alnum:]_@#%:]+:\\)?[ \t]*$")))
+		      "\\>\\)\\)?\\([ \t]*\\|$\\)+\\(.*?\\)\\(:[[:alnum:]_@#%:]+:\\)?[ \t]*$")))
 	 (props (list 'face 'default
 		      'done-face 'org-agenda-done
 		      'undone-face 'default

[-- Attachment #3: Type: text/plain, Size: 14 bytes --]


-- 
 Bastien

next prev parent reply	other threads:[~2012-04-10 17:30 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 [this message]
2012-04-15 20:05   ` Simon Thum
2012-04-16 18:38   ` Simon Thum
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

find likely ancestor, descendant, or conflicting patches for this message:
dfblob:3dd8f88 dfblob:ea5ef7c
	(help)

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=87aa2j4hoj.fsf@gnu.org \
    --to=bzg@gnu.org \
    --cc=Charles.Sebold@lcms.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=simon.thum@gmx.de \
    /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

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