From: Live System User <nyc4bos@aol.com>
To: Glenn Morris <rgm@gnu.org>
Cc: 32443@debbugs.gnu.org
Subject: bug#32443: 27.0.50; encode-time bug
Date: Sat, 22 Sep 2018 00:37:11 -0400 [thread overview]
Message-ID: <87musagnbc.fsf@aol.com> (raw)
In-Reply-To: <87k1o72dmh.fsf@gmail.com> (Robert Pluim's message of "Fri, 31 Aug 2018 09:34:30 +0200")
Robert Pluim <rpluim@gmail.com> writes:
> Live System User <nyc4bos@aol.com> writes:
>
>> Robert Pluim <rpluim@gmail.com> writes:
>
>>> None of those fail for me. Could you tell us which revision youʼre
>>> currently using? Perhaps this got fixed as a side effect of some other
>>> change, in which case I can bisect it.
>>
>> I just tried it using:
>>
>> Repository revision: d8bef4b519624de20baa1428dd103f61dfb220fa
>>
>> and got the same errpneous results.
>
> And thatʼs more recent than my version, so the bug is still lurking
> somewhere.
>
>>>
>>> Otherwise, since youʼre the only one who can reproduce it, could you
>>> do 'edebug-defun' on 'parse-time-string' and step through it? That
>>> might give us a better idea of what's going wrong.
>>
>>
>> I've never used `edebug' before so I will have to get up to speed.
>
> SPC single steps. You can use 'e' to evaluate arbitrary expressions in
> the context of the function youʼre debugging. Since single stepping
> can be tedious, you can move point and use 'h' to run until you reach
> point.
I'm still trying to discover where the bug is using edebug,
Stepping through with edebug everything appears to go fine
with going through all the rules and assigning all of its
resultant values (such as "Tue' equals 2 gleen from
`parse-time-weekdays '), until you get to the following:
(rplaca (nthcdr (pop slots) time) new-val))))))))
Once I execute `rplaca' -- "tike" and "new-val" are incorrect.
FWIW, with thw recwnt update to parse-time.el (Git 0bec064), I now
get
(parse-time-string "Tue, 21 Feb 2017 17:17:56 -0500")
(nil nil nil 21 2 2017 2 -1 nil)
`Before this update, the "-1" was nil.
I believe the "-1" means that DST is not known to be in effect.
DST *is* in effect here.
`Thanks.
>
> Robert
prev parent reply other threads:[~2018-09-22 4:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-14 23:09 bug#32443: 27.0.50; encode-time bug Live System User
2018-08-15 0:00 ` Live System User
2019-09-27 16:34 ` Lars Ingebrigtsen
2019-10-14 7:34 ` Lars Ingebrigtsen
2018-08-21 19:52 ` Live System User
2018-08-24 17:25 ` Glenn Morris
2018-08-29 9:19 ` Robert Pluim
2018-08-29 15:25 ` Live System User
2018-08-30 8:24 ` Robert Pluim
2018-08-30 17:45 ` Live System User
2018-08-31 7:34 ` Robert Pluim
2018-09-22 4:37 ` Live System User [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87musagnbc.fsf@aol.com \
--to=nyc4bos@aol.com \
--cc=32443@debbugs.gnu.org \
--cc=rgm@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.