From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel E. Doherty Subject: Re: Re: Date Prompt Bug (or Anomoly) Date: Tue, 08 Jun 2010 15:45:12 -0500 Message-ID: <87pr012qzr.wl%ded-law@ddoherty.net> References: <876322hcps.wl%ded-law@ddoherty.net> <87k4qfp4ky.fsf@noorul.maa.corp.collab.net> <87fx13p4i5.fsf@noorul.maa.corp.collab.net> <87k4qfuoex.fsf@eee.lan> <0C1D8B23-6AC5-4BC5-806F-43CEE66ECED9@gmail.com> <4C0A8CDA.3000104@ddoherty.net> <7A899B01-66C7-44BF-929A-9E4EED78BE91@gmail.com> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Return-path: Received: from [140.186.70.92] (port=49784 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OM644-0004bd-LW for emacs-orgmode@gnu.org; Tue, 08 Jun 2010 17:10:30 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OM5gs-0007uf-K0 for emacs-orgmode@gnu.org; Tue, 08 Jun 2010 16:46:32 -0400 Received: from micah.ddoherty.net ([74.222.226.122]:51473) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OM5gs-0007d7-EY for emacs-orgmode@gnu.org; Tue, 08 Jun 2010 16:46:30 -0400 In-Reply-To: <7A899B01-66C7-44BF-929A-9E4EED78BE91@gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Carsten Dominik Cc: emacs-orgmode@gnu.org, "Daniel E. Doherty" Carsten, When I tried this last Saturday, I was reluctant to reply since the git server appeared to be down and your message made me think I did not have the latest git version. I tried it again today, and still no joy. I am using org-mode version 6.36a on emacs 23.1 on ubuntu. The latest entry in the Changelog file is ,---- | 2010-06-08 Christian Egli | | * org-taskjuggler.el (org-export-taskjuggler-old-level): | define local variable to avoid compiler warning. `---- The following is straight from an org file: ,---- | Attempted on: <2010-06-08 Tue>. | Entering "3/21": <2021-07-03 Sat>. | Entering "7/21": <2021-07-07 Wed>. `---- I assume that the fix would be in the function org-read-date-analyze, but I see no recent Changelog entries mentioning it. Is it possible this got lost while the git server was down? Regards, Dan Carsten> On Jun 5, 2010, at 7:43 PM, Daniel E. Doherty wrote: >> Carsten, >> >> I pulled the latest git, and it looks like "3/21" and "5/21" work >> as expected. But when I put in "7/21", a date in the near >> future, it is interpreting it a "2021-07-21" rather than the >> "2010-07-21" that one would expect. Carsten> I cannot reproduce this.