From: Mike Kupfer <mike.kupfer@xemacs.org>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: ding@gnus.org
Subject: Re: XEmacs builds failing - gnus-spec.el
Date: Mon, 27 May 2013 17:22:46 -0700 [thread overview]
Message-ID: <201305280022.r4S0MkdU026062@shell0.rawbw.com> (raw)
In-Reply-To: Your message of "Wed, 22 May 2013 14:45:17 +0900." <b4mwqqr36vm.fsf@jpl.org>
Katsumi Yamaoka wrote:
> mike.kupfer@xemacs.org wrote:
[...]
> 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.
That's okay--I appreciate the information about the url code and the
sample workaround code. Thanks.
> > 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.)
Hmm. I don't use Cygwin, so I don't know what the current status is for
XEmacs on Cygwin. Looking in the hg log, I do see this fix, so maybe
it's worth trying again...?
changeset: 5716:1003acd5a4b8
user: Vin Shelton <acs@xemacs.org>
date: Mon Feb 04 20:03:04 2013 -0500
summary: Fix cygwin build on new win32api.
> > 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.
Understood. I'm hoping to get my packaging workflow running smoothly so
that I can track and lightly test development releases of Gnus. (Though
I can't say when I'll get to this.)
best wishes,
mike
next prev parent reply other threads:[~2013-05-28 0:22 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
2013-05-28 0:22 ` Mike Kupfer [this message]
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=201305280022.r4S0MkdU026062@shell0.rawbw.com \
--to=mike.kupfer@xemacs.org \
--cc=ding@gnus.org \
--cc=yamaoka@jpl.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).