From: Thorsten Jolitz <tjolitz@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Setting properties when scrolling around buffer puts property in wrong headline
Date: Fri, 01 Nov 2013 21:33:32 +0100 [thread overview]
Message-ID: <871u2zlv4z.fsf@gmail.com> (raw)
In-Reply-To: CA+M2ft_pfNiq3+sw6N_us1k4aCmHW9+xFZMvVO3s_twBncmVQQ@mail.gmail.com
John Hendy <jw.hendy@gmail.com> writes:
>> 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.
I would say its the expected behaviour - when the mini-buffer is still
active, the command wasn't sent yet, and when you finally send it,
Org-mode acts on the property drawer where point is at that moment.
You might want to read about using the mark, i.e. how to set the mark
before searching the task-id, and then go back to that point before
sending the command from the mini-buffer:
,----------------------------------------------------------------------------------
| http://www.gnu.org/software/emacs/manual/html_node/emacs/Mark-Ring.html#Mark-Ring
`----------------------------------------------------------------------------------
--
cheers,
Thorsten
next prev parent reply other threads:[~2013-11-01 20:33 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
2013-11-01 20:33 ` Thorsten Jolitz [this message]
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=871u2zlv4z.fsf@gmail.com \
--to=tjolitz@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).