Re: Old bug reappearing in 5.8.8

[Colin Marquardt <colin.marquardt@usa.alcatel.com>]

ShengHuo ZHU <zsh@cs.rochester.edu> writes:

> Colin Marquardt <colin.marquardt@usa.alcatel.com> 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