From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: bug#11042: bug#11042: 24.0.94; dangerous org manual: parse-time-months and parse-time-weekdays Date: Fri, 23 Mar 2012 22:46:55 +0100 Message-ID: <87zkb70z3k.fsf__7828.40492106533$1332539181$gmane$org@gnu.org> References: <86wr6htni5.fsf@web.de> <87haxiuk8t.fsf__7447.95193099907$1332338401$gmane$org@altern.org> <87wr6d66so.fsf@web.de> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:36507) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SBCJF-0003s8-Px for emacs-orgmode@gnu.org; Fri, 23 Mar 2012 17:46:11 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SBCJD-0006Lc-Uc for emacs-orgmode@gnu.org; Fri, 23 Mar 2012 17:46:09 -0400 Sender: debbugs-submit-bounces@debbugs.gnu.org Resent-Message-ID: In-Reply-To: <87wr6d66so.fsf@web.de> (Michael Heerdegen's message of "Wed, 21 Mar 2012 21:24:55 +0100") 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: Michael Heerdegen Cc: 11042@debbugs.gnu.org Hi Michael, I removed the part of `org-read-date' docstring about `parse-time-weekdays' and `parse-time-months'. You're right that this can lead too errors. Michael Heerdegen writes: > The thread is not completely visible in google groups, dunno why. > Please read at gnu.emacs.gnus with a newsreader. Done. > The problem was that the user replaced the English names with German > names - instead of adding them to the lists. This broke Gnus. Chances are that this will break Org too. > At least, the documentation in the org manual _must_ be improved, so > that the user is enabled to do the right thing without breaking anything > else. Done. >> Org heavily depends on parse-time.el. Providing a defcustom in Org >> that is tied to parse-time.el at the same time is not trivial. > > Why not? You could just write a function `org-parse-time-string' that > binds `parse-time-months' and `parse-time-weekdays' accordingly and > calls `parse-time-string'. Then you would just need to call this new > function from org code. Actually, there is already `org-parse-time-string', which does not rely on `parse-time-string' at all. Org relies on `parse-time-string' through `org-read-date', a core command of Org. Thanks, -- Bastien