From: Subhan Michael Tindall <SubhanT@familycareinc.org>
To: "'email@example.com'" <firstname.lastname@example.org>
Subject: Adding time to timestamp in agenda view
Date: Mon, 30 Mar 2015 16:49:36 +0000 [thread overview]
Message-ID: <email@example.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1708 bytes --]
I make pretty extensive use of some custom agenda views to manage and schedule my workflow.
Lots of todos with timestamps(Deadlines & Schedules).
It's fairly easy shift deadlines back & forth from agenda view using <Shift right-arrow> and <Shift left-arrow>
There is inconsistency in how this works however.
Deadlines may either simply be a day, or have a time component as well EG <2015-04-11 Sat> or <2015-04-11 Sat 11:00>
The shifted arrow keys move deadlines forward or backward one day by default, carrying any hour:min info right along.
IF there is an hour:min component present, using one or two prefix arguments will shift the hour:min portion forward or backward
IF there is not, bare prefix arguments have no effect
A numeric prefix will always shift the Deadline forward or backward N days
What I would like is a way to ADD an hour:min component to an existing Deadline, and to directly enter an updated hour:min as needed.
Can't seem to find anything that will easily allow this other than moving from the agenda to the source of the headline itself & changing the deadline there.
This message is intended for the sole use of the individual and entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the intended addressee, nor authorized to receive for the intended addressee, you are hereby notified that you may not use, copy, disclose or distribute to anyone the message or any information contained in the message. If you have received this message in error, please immediately advise the sender by reply email and delete the message. Thank you.
[-- Attachment #2: Type: text/html, Size: 4143 bytes --]
reply other threads:[~2015-03-30 16:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).