Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: XEmacs builds failing - gnus-spec.el
Date: Wed, 22 May 2013 14:45:17 +0900	[thread overview]
Message-ID: <b4mwqqr36vm.fsf@jpl.org> (raw)
In-Reply-To: <201305220258.r4M2wk7M060795@shell0.rawbw.com>

[-- Attachment #1: Type: text/plain, Size: 2044 bytes --]

Hi Mike,

mike.kupfer@xemacs.org wrote:
> Katsumi Yamaoka wrote:

>> But please let me say, the fact is that some new Gnus features
>> no longer work on XEmacs (even if the code is compiled with no
>> error).  Typical ones are the features that use url.el.

> Hi Katsumi, is this true for XEmacs 21.5, or just 21.4?  Are these all
> new features in Ma Gnus,

As for url.el originated in W3, the code is too old to use with
Gnus for both 21.5 and 21.4.  I don't think `url-retrieve' that
gnus-compat.el redefines helps.  A workaround attached below is
the one I used to use, but I'm not sure if they are still useful
since I haven't been using XEmacs for a couple of years.  For
the same reason, and since I failed to have taken notes, I don't
recall other matters I faced.  But it is not hard to imagine
there are inconsistencies here and there, since most Gnus
developers are GNU Emacs users and they like to use Emacs' new
features (also it sometimes causes Gnus not to work for old GNU
Emacsen).

> or are older versions of Gnus also affected?

If it is the Gnus XEmacs package, I believe it's safe.  I have
no basis for it, though.

> Are there any bug reports that you can point me at?

I'm no longer suitable for doing it, sorry.  The foremost reason
I got not to use XEmacs is that now I'm using Cygwin for almost
daytime (in the office).  On that platform, I was unable to build
XEmacs 21.5 that works normally.  It frequently crashes.
(Even so, I kept building it periodically keeping track of hg.
 However, it stopped months ago because it got unable to build
 on the latest Cygwin.)

>> As for
>> XEmacs 21.4, I feel it like old GNU Emacsen that Gnus dropped
>> the support long ago.

> Yes, 21.4 is quite old.  If it's too much of a hassle for the Gnus
> developers to support, then maybe it's best to drop support for it.
> Then whatever time is available for XEmacs support can be focused on
> 21.5.

That's good to here from the XEmacs team. :)  The only matter is
that there might be no Gnus developers who use 21.5.

Regards,


[-- Attachment #2: Type: application/emacs-lisp, Size: 1194 bytes --]

  reply	other threads:[~2013-05-22  5:45 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-19 19:23 Adam Sjøgren
2013-05-19 21:45 ` Mike Kupfer
2013-05-19 21:58   ` Adam Sjøgren
2013-05-19 22:13     ` Adam Sjøgren
2013-05-19 23:30       ` Adam Sjøgren
2013-05-20  7:39         ` David Engster
2013-05-20 16:01           ` Adam Sjøgren
2013-05-20 16:36             ` Adam Sjøgren
2013-05-20 23:55               ` Katsumi Yamaoka
2013-05-21 21:01                 ` Adam Sjøgren
2013-05-21 23:39                   ` Katsumi Yamaoka
2013-05-22  2:58                     ` Mike Kupfer
2013-05-22  5:45                       ` Katsumi Yamaoka [this message]
2013-05-28  0:22                         ` Mike Kupfer
2013-05-31 12:07                           ` Mats Lidell
2013-05-22 20:18                     ` Adam Sjøgren
2013-05-22 20:28                       ` Adam Sjøgren
2013-05-22 20:36                     ` David Engster
2013-05-28  0:43                       ` Mike Kupfer
2013-06-01 22:04                         ` XEmacs hash table representation (was XEmacs builds failing - gnus-spec.el) Mike Kupfer
2013-06-02  8:59                           ` David Engster
2013-06-02 16:22                             ` Mike Kupfer
2013-06-06 14:46                               ` Ted Zlatanov
2013-06-06 16:06                                 ` Mike Kupfer
2013-05-22  3:02           ` XEmacs builds failing - gnus-spec.el Mike Kupfer
2013-05-22 20:25             ` David Engster
2013-05-28  0:25               ` 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=b4mwqqr36vm.fsf@jpl.org \
    --to=yamaoka@jpl.org \
    --cc=ding@gnus.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).