From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/67358 Path: news.gmane.org!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.gnus.general Subject: Re: error in gnus-summary-insert-line: gnus-put-text-property has invalid offsets Date: Thu, 11 Sep 2008 07:52:41 -0500 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: <86od2ux2sm.fsf@lifelogs.com> References: <86vdx3opi5.fsf@lifelogs.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1221137643 9735 80.91.229.12 (11 Sep 2008 12:54:03 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 11 Sep 2008 12:54:03 +0000 (UTC) To: ding@gnus.org Original-X-From: ding-owner+M15809@lists.math.uh.edu Thu Sep 11 14:54:59 2008 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from util0.math.uh.edu ([129.7.128.18]) by lo.gmane.org with esmtp (Exim 4.50) id 1KdlhC-00086H-K8 for ding-account@gmane.org; Thu, 11 Sep 2008 14:54:50 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by util0.math.uh.edu with smtp (Exim 4.63) (envelope-from ) id 1KdlfR-0006TN-KT; Thu, 11 Sep 2008 07:53:01 -0500 Original-Received: from mx1.math.uh.edu ([129.7.128.32]) by util0.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1KdlfQ-0006TA-EM for ding@lists.math.uh.edu; Thu, 11 Sep 2008 07:53:00 -0500 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx1.math.uh.edu with esmtp (Exim 4.69) (envelope-from ) id 1KdlfN-00057i-CC for ding@lists.math.uh.edu; Thu, 11 Sep 2008 07:53:00 -0500 Original-Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org) by quimby.gnus.org with esmtp (Exim 3.36 #1 (Debian)) id 1KdlfQ-0001YT-00 for ; Thu, 11 Sep 2008 14:53:00 +0200 Original-Received: from list by ciao.gmane.org with local (Exim 4.43) id 1KdlfJ-0002UY-Uy for ding@gnus.org; Thu, 11 Sep 2008 12:52:53 +0000 Original-Received: from 38.98.147.130 ([38.98.147.130]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 11 Sep 2008 12:52:53 +0000 Original-Received: from tzz by 38.98.147.130 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 11 Sep 2008 12:52:53 +0000 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 38 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 38.98.147.130 X-Face: bd.DQ~'29fIs`T_%O%C\g%6jW)yi[zuz6;d4V0`@y-~$#3P_Ng{@m+e4o<4P'#(_GJQ%TT= D}[Ep*b!\e,fBZ'j_+#"Ps?s2!4H2-Y"sx" User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.0.60 (gnu/linux) Cancel-Lock: sha1:T1C4euZPlDfwRi3kCe0giLZKAzg= X-Spam-Score: -1.5 (-) List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:67358 Archived-At: On Thu, 11 Sep 2008 08:10:47 +0900 Katsumi Yamaoka 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