From mboxrd@z Thu Jan  1 00:00:00 1970
From: Max Mikhanosha <max@openchat.com>
Subject: Re: Bug?: org-agenda-set-property sets property on wrong element
Date: Thu, 28 Jun 2012 06:41:50 -0400
Message-ID: <87zk7nzpjl.wl%max@openchat.com>
References: <871ukz213t.wl%max@openchat.com>
Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([208.118.235.92]:36086)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <max@openchat.com>) id 1SkCAg-0006gN-FQ
	for emacs-orgmode@gnu.org; Thu, 28 Jun 2012 06:42:02 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <max@openchat.com>) id 1SkCAa-00061i-Ar
	for emacs-orgmode@gnu.org; Thu, 28 Jun 2012 06:41:58 -0400
Received: from openchat.com ([75.99.81.170]:37265 helo=momoland.openchat.com)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <max@openchat.com>) id 1SkCAa-00060r-7h
	for emacs-orgmode@gnu.org; Thu, 28 Jun 2012 06:41:52 -0400
Received: from momoland.openchat.com (localhost [127.0.0.1])
	by momoland.openchat.com (Postfix) with ESMTP id 80EA7EACEE
	for <emacs-orgmode@gnu.org>; Thu, 28 Jun 2012 06:41:50 -0400 (EDT)
In-Reply-To: <871ukz213t.wl%max@openchat.com>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: emacs-orgmode@gnu.org

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.