From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Marco Wahl <marcowahlsoft@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [RFC] org-agenda: Jump directly to line in case of a timestamp
Date: Sat, 07 Oct 2017 17:14:21 +0200 [thread overview]
Message-ID: <87mv53gfci.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <84y3onggp3.fsf@gmail.com> (Marco Wahl's message of "Sat, 07 Oct 2017 16:45:12 +0200")
Hello,
Marco Wahl <marcowahlsoft@gmail.com> writes:
> Let's say in an Org file you have the following plain list.
>
> * test
>
> - <2017-10-07 Sat 16:25> Start writing the RFC.
> - <2017-10-07 Sat 16:29> Thought: "Will somebody notice?"
> - <2017-10-07 Sat 16:30> Sent the RFC to the list.
>
> For each list item a corresponding line appears in the day agenda.
>
> .tmp .:16:25...... test
> .tmp .:16:29...... test
> .tmp .:16:30...... test
>
> Pressing TAB in the agenda would jump to the respective plain list item.
>
> Find the concrete patch below.
>
> WDYT?
I have the feeling that both behaviours are useful. All things being
equal, this is the entry being displayed in the Agenda, not necessarily
the line containing the timestamp. Moreover this feature could be less
meaningful if `org-agenda-skip-additional-timestamps-same-entry' is
non-nil.
Maybe an optional argument could allow one to switch from one behaviour
to the other. I have no strong opinion about this, though.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2017-10-07 15:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-07 14:45 [RFC] org-agenda: Jump directly to line in case of a timestamp Marco Wahl
2017-10-07 15:14 ` Nicolas Goaziou [this message]
2017-10-07 16:05 ` Marco Wahl
2017-10-08 3:23 ` Matt Lundin
2017-10-08 6:25 ` Marco Wahl
2017-10-09 6:54 ` Alan Schmitt
2017-10-09 8:19 ` Eric S Fraga
2017-10-09 8:29 ` Alan Schmitt
2017-10-11 11:01 ` Detlef Steuer
2017-10-11 11:42 ` Marco Wahl
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mv53gfci.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=marcowahlsoft@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.