Re: Debugging calendar gremlin in emacs 22.0.50.1

[ken]

Glenn Morris wrote:
> ken wrote:
> 
>> And this is exactly the output of the output I get from the
>> above-invoked "M-x diary" except that the first line (beginning
>> ";-*- mode... is not displayed, and the rest of the lines are
>> single-spaced (see below)-- but if I make this buffer (entitled
>> "Diary for Tuesday, September 19, 2006") the current buffer, do "C-x
>> h M-w" and paste it somewhere, it'll show that first line. Quite
>> weird.
> 
> I don't think there's anything weird here. The standard ("simple")
> diary display uses invisible text to hide parts of the diary buffer.
> So visiting the diary file and displaying the diary buffer give
> different results. Copying and pasting from the simple diary can also
> be confusing. CVS emacs displays a warning header about this by
> default.

I guess my post was too long to get the point across.  Here's my test
diary-file:

---------------------------------------------------------
;-*- mode: lisp; auto-fill-mode: off; fill-column: 999999 -*-

%%(diary-anniversary 9 18 1970) %d years ago it was 9/18/1970

%%(diary-anniversary 9 19 1911) %d years ago it was 9/19/1911

%%(diary-anniversary 9 20 1934) %d years ago it was 9/20/1934

%%(diary-anniversary 9 20 1885) %d years ago it was 9/20/1885

%%(diary-anniversary 9 20 1878) $d years ago it was 9/20/1878

;end of ~/diary.emacs
---------------------------------------------------------

I run M-x diary and this is the output:

-------------------------------------------------------

%%(diary-anniversary 9 18 1970) %d years ago it was 9/18/1970
%%(diary-anniversary 9 19 1911) %d years ago it was 9/19/1911
%%(diary-anniversary 9 20 1934) %d years ago it was 9/20/1934
%%(diary-anniversary 9 20 1885) %d years ago it was 9/20/1885
%%(diary-anniversary 9 20 1878) $d years ago it was 9/20/1878
----------------------------------------------------------

I didn't think that is what it's supposed to do.



> 
>> ....
> 
> I don't think the kernel has anything to do with this error, which is
> unrelated to all the stuff you describe above. So where's the
> backtrace from this sequencep error?

Oh, yeah. the toggle-debug-on-error helped find the problem.  It was a
diary-related thing in my .emacs.  Out of urgency I just commented them
all out for now, so I don't know yet which statement caused the error,
but it's gone now.


> 
> ....