From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/34292 Path: main.gmane.org!not-for-mail From: Colin Marquardt Newsgroups: gmane.emacs.gnus.general Subject: Re: Old bug reappearing in 5.8.8 Date: 16 Jan 2001 13:12:31 -0800 Sender: owner-ding@hpc.uh.edu Message-ID: References: <5br9236ylx.fsf@avocet.cs.rochester.edu> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1035170246 29684 80.91.224.250 (21 Oct 2002 03:17:26 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 03:17:26 +0000 (UTC) Keywords: gnus,texi,info,command,compiling,unknown,free,end Return-Path: Original-Received: from karazm.math.uh.edu (karazm.math.uh.edu [129.7.128.1]) by mailhost.sclp.com (Postfix) with ESMTP id E2365D049D for ; Tue, 16 Jan 2001 16:13:24 -0500 (EST) Original-Received: from sina.hpc.uh.edu (lists@Sina.HPC.UH.EDU [129.7.3.5]) by karazm.math.uh.edu (8.9.3/8.9.3) with ESMTP id PAC22587; Tue, 16 Jan 2001 15:13:09 -0600 (CST) Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Tue, 16 Jan 2001 15:12:21 -0600 (CST) Original-Received: from mailhost.sclp.com (postfix@66-209.196.61.interliant.com [209.196.61.66] (may be forged)) by sina.hpc.uh.edu (8.9.3/8.9.3) with ESMTP id PAA26760 for ; Tue, 16 Jan 2001 15:12:06 -0600 (CST) Original-Received: from netmail.alcatel.com (netmail.alcatel.com [128.251.168.50]) by mailhost.sclp.com (Postfix) with ESMTP id 5B7AFD049D for ; Tue, 16 Jan 2001 16:12:35 -0500 (EST) Original-Received: from relay1.usa.alcatel.com (relay1.usa.alcatel.com [143.209.238.6]) by netmail.alcatel.com (8.9.1/8.9.1) with ESMTP id PAA11063 for ; Tue, 16 Jan 2001 15:12:47 -0600 (CST) Original-Received: from lwmail01.pet.usa.alcatel.com (localhost [127.0.0.1]) by relay1.usa.alcatel.com (8.9.3/8.9.3) with ESMTP id PAA17368 for ; Tue, 16 Jan 2001 15:12:32 -0600 (CST) Original-Received: from optilink.pet.usa.alcatel.com ([10.11.2.49]) by lwmail01.pet.usa.alcatel.com (Netscape Messaging Server 4.15 lwmail01 Aug 8 2000 13:22:32) with ESMTP id G79XM000.GMT for ; Tue, 16 Jan 2001 13:13:12 -0800 Original-Received: from sol-cmarquar.pet.usa.alcatel.com (sol-cmarquar [143.209.122.168]) by optilink.pet.usa.alcatel.com (8.8.8+Sun/8.8.8) with ESMTP id NAA08394 for ; Tue, 16 Jan 2001 13:12:31 -0800 (PST) Original-Received: (from cmarquar@localhost) by sol-cmarquar.pet.usa.alcatel.com (8.9.3+Sun/8.9.1) id NAA21505; Tue, 16 Jan 2001 13:12:32 -0800 (PST) X-Authentication-Warning: sol-cmarquar.pet.usa.alcatel.com: cmarquar set sender to colin.marquardt@usa.alcatel.com using -f X-Draft-From: ("nnimap+nsmail:INBOX" 9242) Original-To: ding@gnus.org In-Reply-To: <5br9236ylx.fsf@avocet.cs.rochester.edu> X-Disclaimer: Opinions expressed are not those of Alcatel USA. User-Agent: Gnus/5.090001 (Oort Gnus v0.01) XEmacs/21.1 (Canyonlands) Precedence: list X-Majordomo: 1.94.jlt7 Original-Lines: 88 Xref: main.gmane.org gmane.emacs.gnus.general:34292 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:34292 ShengHuo ZHU writes: > Colin Marquardt writes: > > > did anyone notice that the old bug from 5.8.3 (AFAIR, fixed in 5.8.4) > > which moved point in the summary buffer after you selected a message > > reappeared in the released 5.8.8 (and thus in Oort too I suppose)? It > > was still fine with my snapshot from 20001122. > > Could you try the latest snapshot? I guess it was introduced in > 20001204, and fixed in 20010112. Thanks, that seems to fix it indeed. While I'm at it, here are some issues I encountered while installing that snapshot (--with-xemacs): ------- The file with the most errors: | While compiling rfc2047-encode-message-header in file /home/sw/cmarquar/emacs/gnus-CURRENT-20010116/lisp/rfc2047.el: | ** reference to free variable enable-multibyte-characters | While compiling rfc2047-encode: | ** reference to free variable enable-multibyte-characters | While compiling rfc2047-b-encode-region: | ** base64-encode-region called with 3 arguments, but accepts only 2 | While compiling rfc2047-decode-region: | ** reference to free variable enable-multibyte-characters | While compiling rfc2047-decode-string: | ** reference to free variable enable-multibyte-characters | While compiling rfc2047-decode: | ** reference to free variable enable-multibyte-characters | While compiling the end of the data: | ** the function charsetp is not known to be defined. enable-multibyte-characters occurs in a lot of files. There are some more assignments to free variables, do you want me to report them all? -------- I don't have makeinfo installed on this Solaris box, so it is running: | xemacs -batch -q -no-site-file -eval '(find-file "gnus.texi")' -eval '(while (re-search-forward "@\\(end \\)?ifnottex" nil t) (replace-match ""))' -l texinfmt -f texinfo-every-node-update -f texinfo-format-buffer -f save-buffer; \ | fi | Making info file `gnus' from `gnus.texi'. | gnus.texi:8: Unknown info command `dircategory'. | gnus.texi:9: Unknown info command `direntry'. | gnus.texi:11: Unmatched `@end'. | gnus.texi:300: Unknown info command `ifnottex'. | gnus.texi:322: Unmatched `@end'. | gnus.texi:413: Unknown info command `detailmenu'. | gnus.texi:869: Bad argument to `end', `detailmenu', using `menu'. | gnus.texi:869: Unmatched `@end'. | gnus.texi:10782: Unknown info command `uref'. | gnus.texi:10782: Misplaced `{'. | gnus.texi:10782: Misplaced `}'. | gnus.texi:12920: Unknown info command `uref'. | gnus.texi:12920: Misplaced `{'. | gnus.texi:12920: Misplaced `}'. | [...repeating several times...] | ./gnus.texi:23454: Node `Key Index''s Next field not pointed back to. | ./gnus.texi:908: This node (`Finding the News') is the one with the bad `Prev'. | *** Error code 2 | make: Fatal error: Command failed for target `gnus' | Current working directory /home/sw/cmarquar/emacs/gnus-CURRENT-20010116/texi | *** Error code 1 | make: Fatal error: Command failed for target `info' -------- It puts an "X-Draft-From:" header to my reply, but on top of all the headers, before the "To:" even. Could this be moved a bit further down? -------- I second that the older "In-Reply-To:" format was nicer. I can get the information from the current format from the "References:" header already. Thanks, Colin