From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: error in gnus-summary-insert-line: gnus-put-text-property has invalid offsets
Date: Wed, 10 Sep 2008 12:54:42 -0500 [thread overview]
Message-ID: <86vdx3opi5.fsf@lifelogs.com> (raw)
I started getting these errors today with a fresh CVS Gnus when entering
any group:
Debugger entered--Lisp error: (args-out-of-range 50 51)
gnus-put-text-property(50 51 gnus-position t)
(if gnus-position (gnus-put-text-property gnus-position (1+ gnus-position) (quote gnus-position) t))
(let (gnus-position) (progn (insert ...) (if ... ...)) (gnus-put-text-property (point) (progn ... ... ... ...) gnus-mouse-face-prop gnus-mouse-face) (progn (insert " " gnus-tmp-subject-or-nil " \n") (if ... ...)) (if gnus-position (gnus-put-text-property gnus-position ... ... t)))
eval((let (gnus-position) (progn (insert ...) (if ... ...)) (gnus-put-text-property (point) (progn ... ... ... ...) gnus-mouse-face-prop gnus-mouse-face) (progn (insert " " gnus-tmp-subject-or-nil " \n") (if ... ...)) (if gnus-position (gnus-put-text-property gnus-position ... ... t))))
gnus-summary-insert-line([0 "" "" "05 Apr 2001 23:33:09 +0400" "" "" 0 0 "" nil] 0 nil t 90 t nil "" nil 1)
gnus-update-summary-mark-positions()
gnus-summary-mode("mygroup")
gnus-summary-setup-buffer("mygroup")
gnus-summary-read-group-1("mygroup" 1 t nil nil nil)
gnus-summary-read-group("mygroup" 1 t nil nil nil nil)
gnus-group-read-group(1 t)
gnus-group-select-group(1)
gnus-topic-select-group(1)
call-interactively(gnus-topic-select-group nil nil)
Interestingly, if I quit the debug output and then retry, it works.
Does anyone know what is causing this? The ChangeLog looks like
gnus-sum.el wasn't updated recently. I'm using Emacs from CVS as well.
Thanks
Ted
next reply other threads:[~2008-09-10 17:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-10 17:54 Ted Zlatanov [this message]
2008-09-10 23:10 ` Katsumi Yamaoka
2008-09-11 12:52 ` Ted Zlatanov
2008-09-15 17:44 ` Ted Zlatanov
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=86vdx3opi5.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).