From: ken <gebser@speakeasy.net>
Subject: Re: Debugging calendar gremlin in emacs 22.0.50.1
Date: Wed, 20 Sep 2006 03:34:06 -0400 [thread overview]
Message-ID: <4510EEEE.4090102@speakeasy.net> (raw)
In-Reply-To: <ok63zenm2.fsf@xoc5.Stanford.EDU>
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.
>
> ....
next prev parent reply other threads:[~2006-09-20 7:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.7084.1158588775.9609.help-gnu-emacs@gnu.org>
2006-09-19 1:59 ` Debugging calendar gremlin in emacs 22.0.50.1 Glenn Morris
2006-09-19 12:19 ` ken
2006-09-20 9:46 ` Peter Dyballa
2006-09-20 11:03 ` ken
[not found] ` <mailman.7132.1158668383.9609.help-gnu-emacs@gnu.org>
2006-09-19 18:07 ` Glenn Morris
2006-09-20 2:10 ` Glenn Morris
2006-09-20 8:29 ` ken
[not found] ` <mailman.7174.1158740998.9609.help-gnu-emacs@gnu.org>
2006-09-20 14:22 ` Edward M. Reingold
2006-09-20 15:01 ` ken
2006-09-20 7:34 ` ken [this message]
2006-09-18 14:12 ken
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4510EEEE.4090102@speakeasy.net \
--to=gebser@speakeasy.net \
/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.
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).