emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Matt Lundin <mdl@imapmail.org>
To: Tom <levelhalom@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Jumping to scheduled item from agend doesn't put cursor on to the heading
Date: Thu, 20 May 2010 15:27:29 -0400	[thread overview]
Message-ID: <87mxvutlum.fsf@fastmail.fm> (raw)
In-Reply-To: <loom.20100519T191546-80@post.gmane.org> (Tom's message of "Wed, 19 May 2010 17:26:49 +0000 (UTC)")

Tom <levelhalom@gmail.com> writes:

> If I jump to a regular TODO item from the agenda then cursor is
> put on the heading line. In case of a scheduled agenda item
> cursor is put to the timestamp. Is it intentional?
>
> I often put text content after the heading and before the
> SCHEDULED timestamp, because I can easily modify the timestamp
> with a hotkey, so it doesn't need to be right after the heading,
> I rather put text content there for convenience. When I jump to
> the heading from the agenda it puts the cursor to the timestamp
> which can be at the end of the heading and it would be more
> useful to have the cursor at the beginning, because my useful
> content is usually there.
>
> Shouldn't jumping from agenda be consistent in this respect and
> put the cursor always on the heading line like it does for
> regular TODO items?
>

I believe this is the intended behavior. You can alter the position of
the cursor by using the following hook:

,----
| org-agenda-after-show-hook is a variable defined in `org-agenda.el'.
| Its value is shown below.
| 
|   This variable is potentially risky when used as a file local variable.
| 
| Documentation:
| Normal hook run after an item has been shown from the agenda.
| Point is in the buffer where the item originated.
`----

Best,
Matt

      reply	other threads:[~2010-05-20 19:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-19 17:26 Jumping to scheduled item from agend doesn't put cursor on to the heading Tom
2010-05-20 19:27 ` Matt Lundin [this message]

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=87mxvutlum.fsf@fastmail.fm \
    --to=mdl@imapmail.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=levelhalom@gmail.com \
    /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).