From: Richard Pieri <ratinox@unilab.dfci.harvard.edu>
Subject: Re: Picons and smileys...
Date: 18 Jun 1996 14:48:42 -0400 [thread overview]
Message-ID: <x7wx157xth.fsf@unilab.dfci.harvard.edu> (raw)
In-Reply-To: "Edward J. Sabol"'s message of Tue, 18 Jun 1996 12:09:16 -0400
-----BEGIN PGP SIGNED MESSAGE-----
>>>>> "EJS" == Edward J Sabol <sabol@thuban.gsfc.nasa.gov> writes:
EJS> All this Gnus development effort going into smileys and picons has
EJS> me depressed -- and envious of all you XEmacs users.
Well, guess what? There are actually XEmacs users who do not use menus
and inlined graphics and all that stuff. We use it because the display
engine is much faster than the FSF's code.
EJS> I really wish RMS or some Emacs hacker would splice in the XEmacs
EJS> display code into Emacs soon! Yeah, yeah, I know: "They're working
EJS> on it."
Actually, they are not. There is no way that the XEmacs X display
engine can be grafted into FSF's code, nor can the Win32 display code be
spliced into XEmacs. Their APIs are about as different as can be. At
one time that might have been possible, like around LEmacs 19.3 or so;
not any more. Since then the two have continuously diverged to the
point where a merger is technically almost impossible.
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3
Charset: noconv
iQCVAwUBMcb6DJ6VRH7BJMxHAQHw0QP+LNm0/JCvLsJb2D6P3TK9akc/MVSDOWQw
XI/PhaFHA1E6eg63WZ3miRb/Puflcnl+ndcQABp3rtrVS5AY7yq5qPP9oEQad2ZJ
kNQNvcU+SQgSMW9gS8o+mSKRhpoL5sxw6SltH/T1uYLbUSc274D5DEQ4VmJGzyHN
QArv1M52fC4=
=YGiU
-----END PGP SIGNATURE-----
--
Richard Pieri/Information Services \ When in doubt, cop an attitude. -A cat's
<ratinox@unilab.dfci.harvard.edu> \ guide to life
http://www.dfci.harvard.edu/ \
prev parent reply other threads:[~1996-06-18 18:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-06-18 16:09 Edward J. Sabol
1996-06-18 16:34 ` Hallvard B Furuseth
1996-06-19 12:18 ` Per Abrahamsen
1996-06-18 18:48 ` Richard Pieri [this message]
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=x7wx157xth.fsf@unilab.dfci.harvard.edu \
--to=ratinox@unilab.dfci.harvard.edu \
/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).