Hi Florian,
Florian Beck writes:
> Missed that. But this reverts commit
> 3ec38f5c064c3270f54876ba33c5ca1097b46853 [1] (in org-map-entries)
>
> I was talking about
> fe3379bda6ca23474639b114592958bf14431c88 [2] (which did the same to
> org-agenda-prepare-buffer)
>
> In fact, the revert *caused*
Florian Beck writes:
> On 05.02.2014 21:59, Nick Dokos wrote:
>
>> John Kitchin reported this last week and Bastien reverted that commit:
>>
>>http://thread.gmane.org/gmane.emacs.orgmode/81587
>
> Missed that. But this reverts commit
> 3ec38f5c064c3270f54876ba33c5ca1097b46853 [1] (in org-map-
On 05.02.2014 21:59, Nick Dokos wrote:
John Kitchin reported this last week and Bastien reverted that commit:
http://thread.gmane.org/gmane.emacs.orgmode/81587
Missed that. But this reverts commit
3ec38f5c064c3270f54876ba33c5ca1097b46853 [1] (in org-map-entries)
I was talking about
fe3379
Florian Beck writes:
> When I call org-map-entries with scope set to 'tree, the current
> heading gets realigned to the top.
>
> Behold:
>
> (org-map-entries (lambda ()
> ;; do something or even nothing
> ) nil 'tree)
>
> I think the culprit is the call to `org-a
When I call org-map-entries with scope set to 'tree, the current heading
gets realigned to the top.
Behold:
(org-map-entries (lambda ()
;; do something or even nothing
) nil 'tree)
I think the culprit is the call to `org-agenda-prepare-buffers', or
rather