[O] org-map-entries broken?

2012-03-19 Thread Charles Sebold
I think this patch may have broken org-map-entries for me: e0072f79137bbfabdf848da6865d8e4de776a549 is the first bad commit commit e0072f79137bbfabdf848da6865d8e4de776a549 Author: David Maus Date:   Sun Mar 18 18:38:50 2012 +0100     Require one or more spaces (+) between keyword and headline  

Re: [O] org-map-entries broken?

2012-03-19 Thread Mike McLean
I can confirm this and add that it additionally breaks tag inheritance. I first noticed that a org-collector code block that I've been using forever was generating table that were way too long. My collector block includes =:conds ( not (string-match-p "noexport" ALLTAGS)= and the extra results I wa

Re: [O] org-map-entries broken?

2012-03-19 Thread Bastien
Mike McLean writes: > I reverted =e0072f79137bbfabdf848da6865d8e4de776a549= and both > behaviors corrected themselves. I reverted this commit both in maint (included in 7.8.06) and master. Thanks, -- Bastien

Re: [O] org-map-entries broken?

2012-03-19 Thread David Maus
At Tue, 20 Mar 2012 02:34:40 +0100, Bastien wrote: > > Mike McLean writes: > > > I reverted =e0072f79137bbfabdf848da6865d8e4de776a549= and both > > behaviors corrected themselves. > > I reverted this commit both in maint (included in 7.8.06) > and master. Thanks, I'll give a fix for the problem I