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: Mon, 15 Sep 2008 12:44:08 -0500 [thread overview]
Message-ID: <86k5ddpamv.fsf@lifelogs.com> (raw)
In-Reply-To: <86od2ux2sm.fsf@lifelogs.com>
On Thu, 11 Sep 2008 07:52:41 -0500 Ted Zlatanov <tzz@lifelogs.com> wrote:
TZ> The error *may* be due to my tinkering with the format, plus maybe my
TZ> special summary prepare hook:
TZ> (add-hook 'gnus-summary-prepare-hook
TZ> (lambda () (set-display-table-slot buffer-display-table
TZ> 'selective-display
TZ> (string-to-vector tzz-mark-threads))))
TZ> which marks threads with "...>>>" (actually Unicode characters, but same
TZ> idea). I don't know for sure, and trapping errors seems to work for
TZ> now, but I'm worried about errors I don't understand :)
I saw a seemingly related issue on emacs-devel and mentioned this one to
Kenichi Handa. We'll see if that bears any fruit...
Ted
prev parent reply other threads:[~2008-09-15 17:44 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
2008-09-15 17:44 ` Ted Zlatanov [this message]
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=86k5ddpamv.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).