From: Nick Dokos <nicholas.dokos@hp.com>
To: Brian van den Broek <brian.van.den.broek@gmail.com>
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: feature suggestion: apply datetime prompt magic to selected region
Date: Fri, 07 Oct 2011 11:42:15 -0400 [thread overview]
Message-ID: <10188.1318002135@alphaville.dokosmarshall.org> (raw)
In-Reply-To: Message from Brian van den Broek <brian.van.den.broek@gmail.com> of "Fri, 07 Oct 2011 16:36:27 +0200." <CAF6Daj+HVoLH-n8M-bDYr2GN5Uu-QUgkqr4OTRGfYE-wL_cn4A@mail.gmail.com>
Brian van den Broek <brian.van.den.broek@gmail.com> wrote:
> ...
> Say I have a buffer with the following contents:
>
> <------>
> Some text in a buffer with orgmode enabled.
>
> Blah blah, Tuesday at 3pm blah blah September 19, 2003, 14:00-15:00 blah blah
> <------>
>
> As it is now, if I kill the text "Tuesday at 3pm", and with cursor
> where I killed hit C-u C-c . to invoke org-time-stamp with prefix
> argument, and then yank the just killed text into the resulting
> prompt, and repeat for the text "Sept. ... 15:00", I get
>
> <------>
> Some text in a buffer with orgmode enabled.
>
> Blah blah, <2011-10-11 Tue 15:00> blah blah <2003-09-19 Fri
> 14:00-15:00> blah blah
> <------>
>
> (the exact way the org-time-stamp command interprets the text is a
> function of the date that it is run and of the value of
> org-read-date-prefer-future, and possibly other variables, too.)
>
> What I was suggesting was it would be cool and a small time-saver if I
> could select the text "Tuesday at 3pm" and hit C-u C-c . and have the
> region replaced with the stamp <2011-10-11 Tue 15:00>, entirely
> bypassing the kill and yank steps. (Achim correctly suggested that
> what I want to do could be done with a keyboard macro. I still think
> it would be neat.)
So we are talking about saving two keystrokes: not worth it in my
opinion for interactive use (unless you have a bunch of things to do, as
you apparently did - macros or a wrapped org-time-stamp assigned to some
key is probably the best solution for that).
The reason why I don't think that anything more needs to be done in org,
is that the major time waster here is *not* the two extra keystrokes:
it's selecting the region(s) to cut/paste - I don't see any way to
improve that.
Nick
next prev parent reply other threads:[~2011-10-07 15:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-06 12:48 feature suggestion: apply datetime prompt magic to selected region Brian van den Broek
2011-10-06 19:46 ` Achim Gratz
2011-10-06 22:38 ` Brian van den Broek
2011-10-07 8:12 ` suvayu ali
2011-10-07 14:36 ` Brian van den Broek
2011-10-07 15:42 ` Nick Dokos [this message]
2011-10-08 7:33 ` suvayu ali
2011-10-24 6:00 ` Bastien
2011-10-25 16:56 ` Brian van den Broek
2011-10-26 7:56 ` Eric S Fraga
2011-10-26 12:00 ` Brian van den Broek
-- strict thread matches above, loose matches on Subject: below --
2011-10-06 12:40 Brian van den Broek
2011-12-28 16:18 ` 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=10188.1318002135@alphaville.dokosmarshall.org \
--to=nicholas.dokos@hp.com \
--cc=brian.van.den.broek@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).