Re: Bug in gnus previewing

[ShengHuo ZHU <zsh@cs.rochester.edu>]

Vladimir Volovich <vvv@vsu.ru> writes:

> Hi!
> 
> This message describes 2 bugs in gnus and a compilation warning.
> 
> 1) a bug in gnus' previewing
> 
>   when i open this message, i see at the end of it:
> 
>  ...
> Content-Transfer-Encoding: base64
> X-MIME-Autoconverted: from 8bit to base64 by ns.ivf.ukrpack.net id VAA34369
> [3. text/rfc822-headers]
> 
>   the button `[3. text/rfc822-headers]' is a false button; it should
>   not've been created, because the part is showed inline; moreover,
>   when i click on that button, i see that button duplicated, and gnus
>   shows messy message.

The button is shown because text/rfc822-headers is not an "automatic"
display part (mm-automatic-display-p).  I've fixed the duplication
problem.

> 
> 2) a bug in mml editing
> 
>   when i edit a message (i removed hash marks) and put several empty
>   lines after <part ...>:
> 
>   <multipart type=mixed>
>   <part type=text/plain nofile=yes>
> 
> 
>   Hi!
> 
>   ... [skipped] ...
> 
>   and then press C-c C-c, gnus removes the empty lines at the
>   beginning of the part. i think that is a bug.

Fixed.

>   Also, when i press C-c C-c, gnus displays raw message instead of a
>   `parsed' message.

The message is encoded in the article buffer, so the raw message is
there.  Sometimes people like to see the raw message after edit. Why
bother to redisplay it?

> 3) compiling current version produces the following warning:
> 
> While compiling the end of the data in file /opt/local/vvv/gnus/lisp/dig.el:
>   ** the function font-lock-set-defaults is not known to be defined.

Fixed.

ShengHuo