|
From: | GNU bug Tracking System |
Subject: | bug#39001: closed (parse-time-string fails to parse Info node's example) |
Date: | Thu, 16 Jan 2020 01:46:02 +0000 |
Your message dated Wed, 15 Jan 2020 17:45:02 -0800 with message-id <address@hidden> and subject line Re: parse-time-string fails to parse Info node's example has caused the debbugs.gnu.org bug report #39001, regarding parse-time-string fails to parse Info node's example to be marked as done. (If you believe you have received this mail in error, please contact address@hidden.) -- 39001: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=39001 GNU Bug Tracking System Contact address@hidden with problems
--- Begin Message ---Subject: parse-time-string fails to parse Info node's example Date: Mon, 6 Jan 2020 22:01:00 -0800 The info node (elisp) Time Parsing suggests that the string "1998-09-12T12:21:54-0200" should be of a format that `parse-time-string` can successfully parse. However, trying to do so produces no useful info from parsing (it returns a list of NILs).GNU Emacs 26.3 (build 1, x86_64-apple-darwin18.5.0, Carbon Version 158 AppKit 1671.4) of 2019-08-29
--- End Message ---
--- Begin Message ---Subject: Re: parse-time-string fails to parse Info node's example Date: Wed, 15 Jan 2020 17:45:02 -0800 Thanks for the bug report. I fixed the code so that it matches the documentation by installing the attached patches into Emacs master. The first patch is the fix, the second is merely refactoring. User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.3.1 0001-parse-time-string-now-parses-ISO-8601-format-strings.patch
Description: Text Data0002-Refactor-parse-time-string.patch
Description: Text Data
--- End Message ---
[Prev in Thread] | Current Thread | [Next in Thread] |