Re: [O] Bug?: org-agenda-set-property sets property on wrong element

[Max Mikhanosha]

At Thu, 28 Jun 2012 06:16:06 -0400,
Max Mikhanosha wrote:
> 
> The problem seems to be that the code like this (with-current-buffer
> buffer (goto-char pos (call-interactively 'some-command)) the point
> inside of 'some-command will not be at `pos', but where the user last
> moved it, _unless_ the buffer's window is selected window, then
> (goto-char) sticks through (call-interactively) boundary.

Above was wrong, it seems the culprit is anything that uses a
completing read from minibuffer, while inside of (with-current-buffer)
for a buffer that is not visible on any window; after reading from
minibuffer the point is reset back to where user last moved it. I was
able to fix parent message's test case by putting save-excursion around
(org-icompleting-read), but I'm wondering if its my specific setup, or
if anyone else can reproduce this.