Re: Agenda Bulk Scatter bug

[Robert Cunningham <robut@iinet.net.au>]

G'day Carsten (and the others who've latched onto this issue),

When I first saw the thread dealing with decode-time ... I frankly had no idea 
how this related to the issue I'd reported. However, a few things have become 
clearer to me and perhaps what I see may help.

Here is what I see on:

GNU Emacs 23.1.50.1 (x86_64-pc-linux-gnu, GTK+ Version 2.18.0) of 2009-09-27 
on crested, modified by Debian

when evaluating in the scratch buffer:

(decode-time (days-to-time (time-to-days (current-time))))
(0 0 8 11 6 3980 3 nil 28800)

and when I use BS on my orgmode (git commit 
c4737ae48b84308e1ac201531aca392a81529974) agenda in this system and item is 
rescheduled as such:

   SCHEDULED: <3980-06-17 Tue>

Eureka! This seems to relate to what Carsten has picked up on.



in ANOTHER Emacs
GNU Emacs 23.1.50.1 (i486-pc-linux-gnu, GTK+ Version 2.12.9) of 2009-08-02 on 
radon, modified by Debian

I see this from the scratch buffer:


(decode-time (days-to-time (time-to-days (current-time))))
[NOTHING RETURNED]

with the following backtrace

Debugger entered--Lisp error: (error "Invalid time specification")
  decode-time((968069 63616))
  eval((decode-time (days-to-time (time-to-days ...))))
  eval-last-sexp-1(t)
  eval-last-sexp(t)
  eval-print-last-sexp()
  call-interactively(eval-print-last-sexp nil nil)



The NOTHING returned here seems consistent with my originally reported 
rescheduling with a lost date.

The main difference between these two Emacs here is one is running on a 64 bit 
(40C date), the other a 32 bit machine (no date).

I can also report that in orgmode 7.5 (release version) there is no problem. 
My uneducated wild guess here would be that some code that somehow "patched" 
the date calculations in 7.5 has been removed or changed so as not to work.

Hope this of some help. I'm not quite in a position to do the git-bisect 
Christian suggested.



Cheers,

RJ Cunningham


On Friday 10 June 2011 16:20:42 Carsten Dominik wrote:
> Hi, I need a few testers:  Something very strange is going on here.
>
> When I evaluate this form
>
> (decode-time (days-to-time (time-to-days (current-time))))
>
>
> I get a date in the year 3980.  I think this used to work.
> Is there anyone who has an idea what is going on here?
>
> Thanks
>
> - Carsten
>
> On Jun 4, 2011, at 6:54 AM, Robert Cunningham wrote:
> > for a few weeks now, and including the git commit
> > af677f6d0667bacba72defeaee7e76557e68f8c8 that I last tested, the Agenda
> > Bulk Scatter (BS) has had a bug whereby items it reschedules have the
> > DATE lost.
> >
> > As an example
> > SCHEDULED 2011-12-12
> >
> > ends up as
> >
> > SCHEDULED
> >
> > after BS
> >
> >
> > org-mode 7.5 did not have the problem
> >
> >
> > Cheers,
> >
> > RJ Cunningham
>
> - Carsten