[PATCH] Fix: (org-agenda-get-progress) Logbook list bullets with 2+ spaces

[PATCH] Fix: (org-agenda-get-progress) Logbook list bullets with 2+ spaces

[Adam Porter]

Previously, logbook list entries with more than one space between the
bullet and the beginning of the entry would be ignored (i.e. if a
bullet is defined in org-list-two-spaces-after-bullet-regexp, two
spaces will be inserted after the bullet, and that prevents
state-changed entries from appearing in the Agenda Log Mode view).

This commit fixes this problem by accepting multiple spaces between
the list bullet and "State" in the state-change regexp.
---
 lisp/org-agenda.el | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el
index eaeddb6..a60fb60 100644
--- a/lisp/org-agenda.el
+++ b/lisp/org-agenda.el
@@ -5733,7 +5733,7 @@ then those holidays will be skipped."
 		 (when (memq 'closed items) (concat "\\<" org-closed-string))
 		 (when (memq 'clock items) (concat "\\<" org-clock-string))
 		 (when (memq 'state items)
-		   (format "- State \"%s\".*?" org-todo-regexp)))))
+		   (format "- +State \"%s\".*?" org-todo-regexp)))))
 	 (parts-re (if parts (mapconcat 'identity parts "\\|")
 		     (error "`org-agenda-log-mode-items' is empty")))
 	 (regexp (concat
-- 
2.7.4

Re: [PATCH] Fix: (org-agenda-get-progress) Logbook list bullets with 2+ spaces

[Nicolas Goaziou]

Hello,

Adam Porter <adam@alphapapa.net> writes:

> Previously, logbook list entries with more than one space between the
> bullet and the beginning of the entry would be ignored (i.e. if a
> bullet is defined in org-list-two-spaces-after-bullet-regexp, two
> spaces will be inserted after the bullet, and that prevents
> state-changed entries from appearing in the Agenda Log Mode view).

I tweaked the commit message to bend it to our conventions and applied
your patch.

Thank you.

Regards,

-- 
Nicolas Goaziou