From: Bastien <bzg@altern.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 11042@debbugs.gnu.org
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 [thread overview]
Message-ID: <87zkb70z3k.fsf__7828.40492106533$1332539181$gmane$org@gnu.org> (raw)
In-Reply-To: <87wr6d66so.fsf@web.de> (Michael Heerdegen's message of "Wed, 21 Mar 2012 21:24:55 +0100")
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 <michael_heerdegen@web.de> 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
next prev parent reply other threads:[~2012-03-23 21:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <86wr6htni5.fsf@web.de>
2012-03-21 14:00 ` bug#11042: 24.0.94; dangerous org manual: parse-time-months and parse-time-weekdays Bastien
[not found] ` <87haxiuk8t.fsf__7447.95193099907$1332338401$gmane$org@altern.org>
2012-03-21 20:24 ` Michael Heerdegen
[not found] ` <87wr6d66so.fsf@web.de>
2012-03-23 21:46 ` Bastien [this message]
2012-03-23 22:27 ` bug#11042: " Bastien
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='87zkb70z3k.fsf__7828.40492106533$1332539181$gmane$org@gnu.org' \
--to=bzg@altern.org \
--cc=11042@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).