From: Greg Troxel <gdt@ir.bbn.com>
To: nicholas.dokos@hp.com
Cc: emacs-orgmode@gnu.org
Subject: Re: bulk rescheduling change?
Date: Wed, 12 Sep 2012 11:49:41 -0400 [thread overview]
Message-ID: <rmibohb5jhm.fsf@fnord.ir.bbn.com> (raw)
In-Reply-To: <7552.1347463418@alphaville> (Nick Dokos's message of "Wed, 12 Sep 2012 11:23:38 -0400")
[-- Attachment #1: Type: text/plain, Size: 1603 bytes --]
Nick Dokos <nicholas.dokos@hp.com> writes:
> Greg Troxel <gdt@ir.bbn.com> wrote:
>
>>
>> I'm running from git, updating every few weeks, currently on
>>
>> commit c276eeebeecba23913547f62cf4b8122f0e8efa9
>> Author: Jambunathan K <kjambunathan@gmail.com>
>> Date: Wed Sep 5 03:33:16 2012 +0530
>>
>> (that commit is surely not relevant to my question...).
>>
>> I often hope to get more done than I do, so I'm often faced with pushing
>> scheduled items forward. I typically do this from the agenda view, with
>> 'C-c C-s' for individual items, and markings and 'B s' for groups of
>> items (typically, saturday-type items to a week later). I find that
>> with individual rescheduling, I get a prompt that has no prefilled text,
>> and can easily type '+1<cr>', or 'sat<cr>'. 'B s' used to behave this
>> way, but now the prompt is prefilled with '<2012-09-12 Wed>', and I have
>> to delete that. This seems like a misfeature, because at least for me
>> bulk-reschedulign to today is not the dominant case, and if it were . is
>> easy to type anwyay. The info file doesn't explain this.
>
> It *should* be the case that you shouldn't have to delete the default:
> just select a date from the calendar or type +2 or type a date and it
> should take that. But in my (rather hastily done) experiment, it
> seemed to ignore any such and in fact, when I tried to reschedule
> again the bunch of things that it rescheduled for today, it would not
> even stop and let me enter anything.
I should have pointed out that I'm running emacs 23.4 inside an xterm.
[-- Attachment #2: Type: application/pgp-signature, Size: 194 bytes --]
next prev parent reply other threads:[~2012-09-12 15:49 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-12 14:19 bulk rescheduling change? Greg Troxel
2012-09-12 15:18 ` Bastien
2012-09-12 15:34 ` Nick Dokos
2012-09-12 15:46 ` Bastien
2012-09-12 15:44 ` Nicolas Goaziou
2012-09-12 15:52 ` Nick Dokos
2012-09-12 16:03 ` Nick Dokos
2012-09-12 16:24 ` Bastien
2012-09-12 17:37 ` Nick Dokos
2012-09-12 15:47 ` Nick Dokos
2012-09-12 16:17 ` Bastien
2012-09-12 16:25 ` Nick Dokos
2012-09-12 16:32 ` Bastien
2012-09-12 17:39 ` Nick Dokos
2012-09-12 18:12 ` Nick Dokos
2012-09-12 18:29 ` Nick Dokos
2012-09-12 20:02 ` Nick Dokos
2012-09-12 20:22 ` Nick Dokos
2012-09-12 21:05 ` Nick Dokos
2012-09-12 23:31 ` Bastien
2012-09-13 2:39 ` Nick Dokos
2012-09-18 17:29 ` Greg Troxel
2012-09-12 22:48 ` Bastien
2012-09-12 22:45 ` Bastien
2012-09-12 15:23 ` Nick Dokos
2012-09-12 15:49 ` Greg Troxel [this message]
2012-09-12 15:57 ` Michael Brand
2012-09-12 23:29 ` Bastien
2012-09-13 5:39 ` Michael Brand
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=rmibohb5jhm.fsf@fnord.ir.bbn.com \
--to=gdt@ir.bbn.com \
--cc=emacs-orgmode@gnu.org \
--cc=nicholas.dokos@hp.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).