From: John Hendy <jw.hendy@gmail.com>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Setting properties when scrolling around buffer puts property in wrong headline
Date: Fri, 1 Nov 2013 14:39:19 -0500 [thread overview]
Message-ID: <CA+M2ft_pfNiq3+sw6N_us1k4aCmHW9+xFZMvVO3s_twBncmVQQ@mail.gmail.com> (raw)
In-Reply-To: <CA+M2ft-LAKFmRT=R3=wSQAuPY0F1Q0y8RRYndMK2X-r+Sm-0Ag@mail.gmail.com>
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 <jw.hendy@gmail.com> 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.
next prev parent reply other threads:[~2013-11-01 19:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-27 4:11 Setting properties when scrolling around buffer puts property in wrong headline John Hendy
2013-11-01 19:39 ` John Hendy [this message]
2013-11-01 20:33 ` Thorsten Jolitz
2013-11-03 14:22 ` John Hendy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+M2ft_pfNiq3+sw6N_us1k4aCmHW9+xFZMvVO3s_twBncmVQQ@mail.gmail.com \
--to=jw.hendy@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).