From mboxrd@z Thu Jan 1 00:00:00 1970 From: Max Mikhanosha Subject: Bug?: org-agenda-set-property sets property on wrong element Date: Thu, 28 Jun 2012 06:16:06 -0400 Message-ID: <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: Received: from eggs.gnu.org ([208.118.235.92]:49873) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SkBlj-0000vS-OC for emacs-orgmode@gnu.org; Thu, 28 Jun 2012 06:16:19 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SkBli-0001KP-18 for emacs-orgmode@gnu.org; Thu, 28 Jun 2012 06:16:11 -0400 Received: from openchat.com ([75.99.81.170]:38639 helo=momoland.openchat.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SkBlh-0001Jw-MM for emacs-orgmode@gnu.org; Thu, 28 Jun 2012 06:16:09 -0400 Received: from momoland.openchat.com (localhost [127.0.0.1]) by momoland.openchat.com (Postfix) with ESMTP id E614AEAD6E for ; Thu, 28 Jun 2012 06:16:06 -0400 (EDT) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 Can someone confirm this, before I try to fix this? 1. Generate agenda 2. Go to some entry A by pressing RET 3. Switch back to agenda, and make sure its the only window (or that A's buffer is not in any other window) 4. In Agenda navigate to entry B (in the same buffer as A), and C-c C-x p (org-agenda-set-property), use any property name or value Result: property is set in entry A not in entry B. This is with org-mode from git, and emacs 23. 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. Could be that there are other pieces of code like this in lurking in there. Regards, Max