Gnus development mailing list
 help / color / mirror / Atom feed
From: Alan Shutko <ats@acm.org>
Cc: ding@gnus.org
Subject: Re: pgnus and GNU emacs 20.3 and XEmacs 20.4 and byte-compile
Date: 26 Sep 1998 11:30:11 -0500	[thread overview]
Message-ID: <m3ogs2q1kc.fsf@hubert.wuh.wustl.edu> (raw)
In-Reply-To: Hrvoje Niksic's message of "26 Sep 1998 17:18:57 +0200"

>>>>> "H" == Hrvoje Niksic <hniksic@srce.hr> writes:

H> If the question is not personal, I'd like to know why?  I could
H> imagine that you would do the reverse (FSF for Gnus, XEmacs for the
H> rest) because of the speed difference, but if XEmacs is good enough
H> for Gnus, why not run it for the rest of your editing tasks?

My guess would be that he likes inline images, but for whatever
reason, doesn't like the rest of XEmacs.  For me, the large numbers of
differences between Emacs and XEmacs annoy the hell out of me and I
find my blood pressure increasing way too much... I know Emacs very
well, and would have to spend so much time learning the changes in
XEmacs that it's not worth it for me.  It's not that XEmacs has any
major flaws, but just billions of little differences.  Way too much
for me to worry about for the sake of proportional fonts and inline
images (for which I can wait until Emacs 20.5).

-- 
Alan Shutko <ats@acm.org> - By consent of the corrupted
Visit beautiful Wisconsin Dells.


  reply	other threads:[~1998-09-26 16:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-09-26 14:50 Steinar Bang
1998-09-26 15:18 ` Hrvoje Niksic
1998-09-26 16:30   ` Alan Shutko [this message]
1998-09-26 16:49     ` Hrvoje Niksic
1998-09-27 13:20     ` Steinar Bang
1998-09-27 16:50       ` Jan Vroonhof
1998-09-28 10:03         ` Steinar Bang
1998-09-28 10:06   ` Steinar Bang
1998-09-28 15:04     ` Alan Shutko
1998-09-29 14:53     ` Hrvoje Niksic

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=m3ogs2q1kc.fsf@hubert.wuh.wustl.edu \
    --to=ats@acm.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).