From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Hendy Subject: Re: Setting properties when scrolling around buffer puts property in wrong headline Date: Fri, 1 Nov 2013 14:39:19 -0500 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:41155) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VcKYz-0003iN-CN for emacs-orgmode@gnu.org; Fri, 01 Nov 2013 15:39:22 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VcKYy-0008CV-Ch for emacs-orgmode@gnu.org; Fri, 01 Nov 2013 15:39:21 -0400 Received: from mail-oa0-x22f.google.com ([2607:f8b0:4003:c02::22f]:54865) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VcKYy-0008CP-6m for emacs-orgmode@gnu.org; Fri, 01 Nov 2013 15:39:20 -0400 Received: by mail-oa0-f47.google.com with SMTP id i1so4977092oag.20 for ; Fri, 01 Nov 2013 12:39:19 -0700 (PDT) In-Reply-To: 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 Bump... at the least, wondering if this is intended/expected, or if it's a genuine issue. Perhaps no one else encounters this? John On Sat, Oct 26, 2013 at 11:11 PM, John Hendy wrote: > Greetings, > > > I'm supposing there's no way around this... but I'm creating a > taskjuggler document that's fairly wrong. I often find myself in a > situation where I go to set a :depends: property to reference another > headline and need to go see what it's task_id is. So, I scroll down, > look at the task, then enter the correct task_id in the minibuffer > (which is still active after doing C-c C-x p property-name RET), and > then find that it's been inserted in a different headline since > scrolling moves the point/cursor to a different headline. > > Again, I'm thinking that Emacs just works differently than other > programs in that the cursor appears to move to stay in the view of the > current buffer vs. staying at the existing point regardless of where > I'm looking in the file. > > Is there a way around this issue? Almost like remembering the MARK > where either 1) the command was initiated or 2) where it was when the > property name was typed, followed by RET (but prior to setting the > value) vs. wherever the cursor ends up between setting the property > name and actually setting the value? > > > Thanks! > John > > P.S. if the issue is unclear, open up a longer Org document and unfold > enough headlines so that the entire file cannot be viewed within the > height. Go a headline near the top and do C-c C-x p. Type a property > name and press RET. Now scroll down a bit in the buffer and then type > in the name of the property and press RET. The property will be > inserted in whatever headline you're cursor scrolled down to, not the > headline in which you initiated the command.