From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: calendar date adjustments blocked Date: Sat, 5 Nov 2011 07:26:57 +0100 Message-ID: <0376B403-8F85-412C-84BD-285C7619E3BC@gmail.com> References: <6690.1320458628@alphaville.dokosmarshall.org> Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([140.186.70.92]:59615) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RMZid-0004JQ-6E for emacs-orgmode@gnu.org; Sat, 05 Nov 2011 02:27:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RMZib-0002Xw-GD for emacs-orgmode@gnu.org; Sat, 05 Nov 2011 02:27:06 -0400 Received: from mail-ey0-f169.google.com ([209.85.215.169]:38808) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RMZib-0002Xo-3I for emacs-orgmode@gnu.org; Sat, 05 Nov 2011 02:27:05 -0400 Received: by eye4 with SMTP id 4so3000629eye.0 for ; Fri, 04 Nov 2011 23:27:04 -0700 (PDT) In-Reply-To: <6690.1320458628@alphaville.dokosmarshall.org> 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: Jude DaShiell , emacs-orgmode@gnu.org On 5.11.2011, at 03:03, Nick Dokos wrote: > Jude DaShiell wrote: >=20 >> I needed to enter information for two dates in org-mode and went into=20= >> calendar using c-c+! and got the current date as expected then hit = c-b to=20 >> move the date to yesterday and pointer remained on today's date. So = I=20 >> ended up hitting on today's date and editing it in the actual = org=20 >> file and filling the rest of my entry in after it. Then I repeated = the=20 >> operation for today and entered today's information. I was a bit=20 >> surprised that the date was locked like that once calendar mode was=20= >> entered but managed a workaround anyway. >>=20 >=20 > I guess your problem is that the calendar is indeed popped up, but the = cursor > is still in the daytime prompt in the minibuffer. As Bernt points out, = typing > -2 at that point gets you to the right date. >=20 > The calendar seems to be for inveterate mouser users, not keyboard > types: even if I C-x o to the calendar window, the cursor ends up not = on > today's date but off to the right somewhere and I get an error = message: >=20 > ,---- > | Error in post-command-hook (org-read-date-display): = (buffer-read-only *Calendar*) > `---- >=20 > Not sure what's going on there: I expected that after I switched = windows > to the Calendar, my cursor would be on today's date. The popup calender in Org is a special construct that hijacks key = presses so that all control can be done from the minibuffer, without switching = to the calender buffer itself. This has side effects if you try to move into the calendar buffer window anyway. Bernt showed one way to specify the date. You can also click on the = date to get it selected immediately. Or you can use S-left twice to get the = date selected with the shadow cursor in the calendar window. There are more key presses that manipulate the calendar window from the minibuffer, see http://orgmode.org/manual/Creating-timestamps.html#Creating-timestamps HTH - Carsten