Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
Cc: Mike Kupfer <kupfer@athyra.sfbay.sun.com>,
	ding@gnus.org, XEmacs Beta <xemacs-beta@xemacs.org>
Subject: Re: [Bug: 21.4.18] gnus 5.10.7 not rendering Latin-1 headers
Date: Mon, 20 Feb 2006 10:41:33 +0100	[thread overview]
Message-ID: <v9d5hi4baq.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <87mzgmquy4.fsf@tleepslib.sk.tsukuba.ac.jp> (Stephen J. Turnbull's message of "Mon, 20 Feb 2006 17:46:11 +0900")

On Mon, Feb 20 2006, Stephen J. Turnbull wrote:

>>>>>> "Reiner" == Reiner Steib <reinersteib+gmane@imap.cc> writes:
>
>     Reiner> In case it wasn't obvious: mm-coding-system-list (the
>     Reiner> function) is aliased to "ignore" if (fbound
>     Reiner> 'coding-system-list) is nil.
>
> So mm-coding-system-p passes nil back to Gnus.

Yes, this is what the current mm-util.el code does in Mike's XEmacs.

>     Reiner> Leaving this for the XEmacs folks...
>
>     >> What should (mm-coding-system-p 'iso-8859-1) return in non-MULE
>     >> XEmacs?
>
> nil, according to Reiner's description of the design.  So Gnus is
> receiving nil as a result from an internal Gnus function, and refusing
> to handle that value, which eventually results in an error and buggy
> display.

Huh, I didn't describe the design, I only described the current code.
I don't know if the current code is correct for XEmacs or gives the
desired result there.

> This is definitely not an XEmacs problem---it's all internal to Gnus.
>
> So I guess Reiner is saying that no-MULE XEmacs is not supported by
> Gnus any more.

Stephen, I don't understand this finger pointing.  It doesn't bring us
any further.  If you look at Gnus' ChangeLog you won't find any
changes aiming to stop supporting no-MULE XEmacs.  There are only very
few XEmacs specific changes in that area, AFAICS.  Most of these were
patches from Aidan WRT latin-unity (I don't know if those are
responsible for Mike's problems or not).  If support of no-MULE XEmacs
has been broken, it wasn't done on purpose and as I wrote in my
previous mail, I'm all for fixing it if someone gives us an idea how
to fix it.

BTW, we are talking about the Gnus 5.10.x series which (compared to
5.10.1) should not contain any new features (only bugfixes).  We
didn't even officially drop support for Emacs 20.7 and XEmacs 21.1, see
<http://thread.gmane.org/v9y80ega32.fsf_-_@marauder.physik.uni-ulm.de>.
But I doubt that anyone verified that the current v5-10 branch works
on these Emacsen.

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/



  reply	other threads:[~2006-02-20  9:41 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200601280127.k0S1RqD7007468@athyra.sfbay.sun.com>
     [not found] ` <87irs44xm9.fsf@tleepslib.sk.tsukuba.ac.jp>
2006-01-29 20:05   ` Reiner Steib
2006-01-29 22:24     ` Steve Youngs
2006-01-29 22:40       ` Reiner Steib
2006-01-30  1:16         ` Stephen J. Turnbull
2006-02-17 22:13           ` Date of XEmacs' Gnus (5.10.7) package (was: [Bug: 21.4.18] gnus 5.10.7 not rendering Latin-1 headers) Reiner Steib
2006-01-30 23:24         ` [Bug: 21.4.18] gnus 5.10.7 not rendering Latin-1 headers Mike Kupfer
2006-01-30 23:39       ` where does package-get-info get its info from? (was: gnus 5.10.7 not rendering Latin-1 headers) Mike Kupfer
2006-01-31  1:11         ` where does package-get-info get its info from? Steve Youngs
2006-02-18  0:34     ` [Bug: 21.4.18] gnus 5.10.7 not rendering Latin-1 headers Mike Kupfer
2006-02-18 14:55       ` Stephen J. Turnbull
2006-02-19 12:48         ` Reiner Steib
2006-02-19 22:11           ` Mike Kupfer
2006-02-19 23:22             ` Reiner Steib
2006-02-20  7:41               ` Katsumi Yamaoka
2006-02-20  9:40                 ` Katsumi Yamaoka
2006-02-20 11:30                   ` Katsumi Yamaoka
2006-02-20 19:20                     ` Mike Kupfer
2006-02-21 18:29                     ` Mike Kupfer
2006-02-20  8:46               ` Stephen J. Turnbull
2006-02-20  9:41                 ` Reiner Steib [this message]
2006-02-20 15:52                   ` Stephen J. Turnbull
2006-02-20 21:26                     ` Miles Bader
2006-04-09  8:14                   ` Aidan Kehoe
2006-04-11 18:35                     ` Reiner Steib
2006-04-13 22:34                       ` Mike Kupfer
2006-04-14  8:14                         ` Stephen J. Turnbull
     [not found] <17990.13620.262943.353149@parhasard.net>
2007-05-13  9:20 ` Gnus: Autoloads for parse-time.el variables (was: [PATCH] package building problems.) Reiner Steib
2007-05-13 12:45   ` Aidan Kehoe
2007-05-14 17:21   ` Mike Kupfer
     [not found] <m33awph096.fsf@Overgaard.mail.dk>
     [not found] ` <878x6g6yz7.fsf@uwakimon.sk.tsukuba.ac.jp>
2007-10-06 16:09   ` [Bug: 21.5-b28] XEmacs/gnus refuses to open newsgroup with identical messages Reiner Steib
2007-10-07 13:47     ` Thomas Overgaard
2007-10-09 21:13     ` gnus 5.10.8 for XEmacs (was [Bug: 21.5-b28] XEmacs/gnus refuses to open newsgroup with identical messages) Mike Kupfer

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=v9d5hi4baq.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --cc=ding@gnus.org \
    --cc=kupfer@athyra.sfbay.sun.com \
    --cc=xemacs-beta@xemacs.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).