From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: error in gnus-summary-insert-line: gnus-put-text-property has invalid offsets
Date: Thu, 11 Sep 2008 07:52:41 -0500 [thread overview]
Message-ID: <86od2ux2sm.fsf@lifelogs.com> (raw)
In-Reply-To: <b4mbpyvlhqg.fsf@jpl.org>
On Thu, 11 Sep 2008 08:10:47 +0900 Katsumi Yamaoka <yamaoka@jpl.org> wrote:
KY> I guess the format spec registered in the ~/.newsrc.eld file has
KY> been changed; it might have happened when you tried modifying
KY> gnus-spec.el.
KY> Cf. http://news.gmane.org/group/gmane.emacs.gnus.general/thread=67228
KY> There might have been something wrong in the patch I posted.
KY> The format spec that is computed from `gnus-summary-line-format'
KY> will not be updated unless the value of `gnus-summary-line-format'
KY> is changed or evaluating the form:
KY> (gnus-update-format-specifications t 'summary)
KY> Could you try this? (Performing this should be always safe.)
KY> If it does the trick, you had better do it for `group' as well:
KY> (gnus-update-format-specifications t 'group)
That didn't do anything. The spec, and why it's cached in the newsrc
file, are a mystery to me. I comitted a patch to trap errors on setting
that property, since the error is harmless (but we do generate a
gnus-message warning about it).
The error *may* be due to my tinkering with the format, plus maybe my
special summary prepare hook:
(add-hook 'gnus-summary-prepare-hook
(lambda () (set-display-table-slot buffer-display-table
'selective-display
(string-to-vector tzz-mark-threads))))
which marks threads with "...>>>" (actually Unicode characters, but same
idea). I don't know for sure, and trapping errors seems to work for
now, but I'm worried about errors I don't understand :)
Ted
next prev parent reply other threads:[~2008-09-11 12:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-10 17:54 Ted Zlatanov
2008-09-10 23:10 ` Katsumi Yamaoka
2008-09-11 12:52 ` Ted Zlatanov [this message]
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=86od2ux2sm.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).