From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Matt Lundin <mdl@imapmail.org>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: Point jumps when changing timestamps
Date: Thu, 04 Aug 2011 20:06:18 +0200 [thread overview]
Message-ID: <87aabpyrtx.fsf@gmail.com> (raw)
In-Reply-To: <87oc05f7x7.fsf@fastmail.fm> (Matt Lundin's message of "Thu, 04 Aug 2011 11:39:00 -0500")
Matt Lundin <mdl@imapmail.org> writes:
> A bit more generous org-at-timestamp-p does have some practical
> advantages: it can save cursor movement when navigating an org document.
> For instance, when navigating the following headline, I would typically
> type C-n C-e to go to the end of the scheduled line. That puts the
> cursor at the point directly after the scheduled timestamp:
>
> * A headline
> SCHEDULED: <2011-08-04 Thu>
> ^ i.e., here
>
> Having to move the cursor backwards one point would add a little bit of
> inconvenience.
C-c C-s on the headline lets you modify more quickly the
time-stamp. I may be missing the point, but that position has no
particular interest.
> I believe the current behavior of org-at-timestamp-p is consistent with
> that of the *-at-point functions.
Agreed. But, on the other hand, it isn't consistent with any similar Org
function. Try `org-footnote-at-reference-p' just after a footnote
reference or `org-context' just after a link. In both cases, point will
be considered outside of the element.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2011-08-04 18:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-03 14:18 Point jumps when changing timestamps Matt Lundin
2011-08-04 16:01 ` Nicolas Goaziou
2011-08-04 16:39 ` Matt Lundin
2011-08-04 18:06 ` Nicolas Goaziou [this message]
2011-08-04 18:45 ` Matt Lundin
2011-08-05 8:47 ` Nicolas Goaziou
2011-08-05 14:08 ` Matt Lundin
2011-08-15 8:22 ` Bastien
2011-08-15 8:11 ` Bastien
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=87aabpyrtx.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mdl@imapmail.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).