From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: bug#11042: 24.0.94; dangerous org manual: parse-time-months and parse-time-weekdays Date: Wed, 21 Mar 2012 15:00:34 +0100 Message-ID: <87haxiuk8t.fsf@altern.org> References: <86wr6htni5.fsf@web.de> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:43767) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SAM4W-0000eZ-Vx for emacs-orgmode@gnu.org; Wed, 21 Mar 2012 09:59:35 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SAM4P-0002sQ-Nc for emacs-orgmode@gnu.org; Wed, 21 Mar 2012 09:59:28 -0400 Sender: debbugs-submit-bounces@debbugs.gnu.org Resent-Message-ID: In-Reply-To: <86wr6htni5.fsf@web.de> (Michael Heerdegen's message of "Mon, 19 Mar 2012 01:58:42 +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@web.de Cc: 11042@debbugs.gnu.org Hi Michael, Michael Heerdegen writes: > The org-mode manual under the node "The date/time prompt" tells: > > "[...] The function understands English month and weekday abbreviations. If > you want to use unabbreviated names and/or other languages, configure > the variables `parse-time-months' and `parse-time-weekdays'." > > It doesn't tell how the user can do that. Even worse, > `parse-time-months' and `parse-time-weekdays' are not defined as user > options and undocumented! > > After reading the above section in the org manual, users may replace > the English names with e.g. German ones in their config. Seems this > is not a good idea, as this user question in gnu.emacs.gnus shows: > > http://groups.google.com/group/gnu.emacs.gnus/browse_thread/thread/8dde85b5ff3ab454/a02ddb878bfa1eb9 The thread doesn't tell what is wrong with setting `parse-time-months' and `parse-time-weekdays'. Can you expand a bit more on this? > BTW1: maybe a better solution would be to define own variables for > this purpose in org, instead of letting users change variables in > parse-time.el. 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. Thanks, -- Bastien