Gnus development mailing list
 help / color / mirror / Atom feed
From: Dave Love <d.love@dl.ac.uk>
Cc: Jan Vroonhof <jan@xemacs.org>, ding@gnus.org
Subject: Re: That old flamewar again [was Re: recent smiley.el changes]
Date: 27 Feb 2002 19:59:41 +0000	[thread overview]
Message-ID: <rzqn0xupufm.fsf@djlvig.dl.ac.uk> (raw)
In-Reply-To: <rjeljd8jdv.fsf@ssv2.dina.kvl.dk>

Per Abrahamsen <abraham@dina.kvl.dk> writes:

> Where did you contact the XEmacs maintainers about a common image
> API?

I didn't.  I got the history when I went to implement image features.
I don't see why details are important or why people think I'd make it
up.

> I searched the xemacs-beta archives and couldn't find it there.

I wouldn't have expected to find it there, but see
<URL:http://list-archive.xemacs.org/xemacs-beta/199809/msg00370.html>.
Note that was before core Emacs developers knew about it.
The subsequent exchange that caused the bad feeling was not there.

It's clear from that archive that XEmacs people had access
specifically to the Emacs 21 image API (which became image.el) and to
Emacs pretest source.  You can also see Gerd's collaboration over the
hash table API, but not other exchanges he and I (at least) had.
These often just made us more circumspect.  There's obviously plenty
on that list about Emacs and its developers which is misleading at
best.

This is now definitely not relevant to Gnus, even considering the
connexion of Bill Perry's work on inline images (which exhibited the
image API originally on the ding list).



  parent reply	other threads:[~2002-02-27 19:59 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-31  1:31 recent smiley.el changes Wes Hardaker
2002-02-01  1:48 ` Steve Youngs
2002-02-01 16:53   ` Wes Hardaker
2002-02-11 11:56     ` Han Pilmeyer
2002-02-11 20:26       ` Steve Youngs
2002-02-12 15:30         ` Han Pilmeyer
2002-02-13 15:32           ` Wes Hardaker
2002-02-11 18:43 ` Dave Love
2002-02-12 16:18   ` That old flamewar again [was Re: recent smiley.el changes] Jan Vroonhof
2002-02-20 19:52     ` Dave Love
2002-02-20 19:52     ` Dave Love
2002-02-22 18:24       ` Per Abrahamsen
2002-02-27 19:59         ` Dave Love
2002-02-27 19:59         ` Dave Love [this message]
2002-02-22 18:24       ` Per Abrahamsen
2002-02-24 14:15       ` Fabrice Popineau
2002-02-26 16:11         ` Kai Großjohann
2002-02-27 19:18           ` Fabrice Popineau
2002-02-27 19:18           ` Fabrice Popineau
2002-02-26 16:11         ` Kai Großjohann
2002-02-27 20:10         ` Dave Love
2002-02-27 21:25           ` Kai Großjohann
2002-03-04  7:51             ` Fabrice Popineau
2002-03-04  7:51             ` Fabrice Popineau
2002-02-27 21:25           ` Kai Großjohann
2002-02-27 20:10         ` Dave Love
2002-02-24 14:15       ` Fabrice Popineau

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=rzqn0xupufm.fsf@djlvig.dl.ac.uk \
    --to=d.love@dl.ac.uk \
    --cc=ding@gnus.org \
    --cc=jan@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).