Gnus development mailing list
 help / color / mirror / Atom feed
From: Hrvoje Niksic <hniksic@srce.hr>
Subject: Re: using pop3.el instead of
Date: 06 Apr 1997 21:02:12 +0200	[thread overview]
Message-ID: <kigafncm0uj.fsf@jagor.srce.hr> (raw)
In-Reply-To: Steinar Bang's message of 06 Apr 1997 20:10:11 +0200

Steinar Bang <sb@metis.no> writes:

> Trying to accomodate Xemacs, I had temporarily removed Gnus 5.4.25
> from the load-path of GNU Emacs 19.34, so I was running 5.3 there
> instead (what exactly are the incompatibles of .elc files of Xemacs
> 19.15 and GNU Emacs 19.34?  Do the latter need Lars' patches to
> coexist?).

The best way to share Lisp code between the two is to byte-compile in
XEmacs.  This may sound XEmacs-centric, but it's not intended to be.
Emacs 19.35 and XEmacs 19.15 will be better at sharing byte-code, I
think.

Another reason not to use Gnus 5.3 in XEmacs is that you don't get the
toolbar and icons and all the gooey stuff.

I byte-compile Gnus with XEmacs, and can run it from GNU Emacs
normally.  But then again, XEmacs is my regular environment, so I'm
biased. :-(

-- 
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
Contrary to popular belief, Unix is user friendly.  
It just happens to be selective about who it makes friends with.


  reply	other threads:[~1997-04-06 19:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-04-04 19:21 Steinar Bang
1997-04-04 23:09 ` Stainless Steel Rat
1997-04-06 18:00   ` Steinar Bang
1997-04-07 16:32     ` Stainless Steel Rat
1997-04-06 18:10   ` Steinar Bang
1997-04-06 19:02     ` Hrvoje Niksic [this message]
1997-04-07  7:21     ` Steinar Bang
1997-04-07  8:20       ` Kai Grossjohann
1997-04-07 16:38       ` Stainless Steel Rat
     [not found] ` <r9q67y21kip.fsf@teapotdome.cs.washington.edu>
1997-04-06 17:06   ` Steinar Bang

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=kigafncm0uj.fsf@jagor.srce.hr \
    --to=hniksic@srce.hr \
    /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).