From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: bulk rescheduling change? Date: Thu, 13 Sep 2012 01:31:53 +0200 Message-ID: <87oblaq0ly.fsf@altern.org> References: <87mx0vi81a.fsf@altern.org> <8103.1347464053@alphaville> <8419.1347464859@alphaville> <87ligfxlk1.fsf@altern.org> <9459.1347467106@alphaville> <87627jxkvs.fsf@altern.org> <2861.1347471570@alphaville> <3596.1347473565@alphaville.americas.hpqcorp.net> <3920.1347474577@alphaville.americas.hpqcorp.net> <5589.1347480129@alphaville.americas.hpqcorp.net> <5838.1347481364@alphaville.americas.hpqcorp.net> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:48823) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TBwPS-0004Ph-NF for emacs-orgmode@gnu.org; Wed, 12 Sep 2012 19:31:55 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TBwPR-0005eP-Ex for emacs-orgmode@gnu.org; Wed, 12 Sep 2012 19:31:54 -0400 Received: from mail-wi0-f171.google.com ([209.85.212.171]:59172) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TBwPR-0005cv-8X for emacs-orgmode@gnu.org; Wed, 12 Sep 2012 19:31:53 -0400 Received: by wibhq4 with SMTP id hq4so4896073wib.12 for ; Wed, 12 Sep 2012 16:31:52 -0700 (PDT) In-Reply-To: <5838.1347481364@alphaville.americas.hpqcorp.net> (Nick Dokos's message of "Wed, 12 Sep 2012 16:22:44 -0400") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: nicholas.dokos@hp.com Cc: emacs-orgmode@gnu.org Hi Nick, Nick Dokos writes: > Well, the non-interactiveness and the next day are because the four > items I marked were the last four items for that date, so after marking > them, the cursor happened to be on the date line for the next day, which > apparently is taken as an indication that I want things to be > rescheduled for that date, no questions asked. Not sure I like this > much. This implementation was to mimick the previous behavior we had with `k m' (to mark an entry) then `k s' (to schedule it to the date at point with no prompt.) I don't like having no prompt here too. I just changed the behavior so that there is *always* a prompt with `m m m B s' -- if the cursor is on a date, this date is the default time for the prompt, RET will reschedule to this date. > However, if I move the cursor off the date line before I issue the > bulk command, I get a date dialog, but it's a no-op: no matter what > I give it, things are rescheduled to today. Fixed. Thanks! -- Bastien