Gnus development mailing list
 help / color / mirror / Atom feed
From: Cyrille Lefevre <clefevre%no-spam@citeweb.net>
Subject: Re: Gnus v5.8.7 is released
Date: 11 Jul 2000 12:39:55 +0200	[thread overview]
Message-ID: <r991q7b8.fsf@pc166.gits.fr> (raw)
In-Reply-To: <vaf4s5xw1bz.fsf@lucy.cs.uni-dortmund.de>

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> Cyrille Lefevre <clefevre%no-spam@citeweb.net> writes:
> 
> > can someone explain to me the difference between GNUS (the old one
> > ?), Gnus (the newer one ?) and the one w/ Xemacs ? as I undertood in
> > the web pages, GNUS is dead, God saves Gnus :) but what about the
> > Xemacs version ?
> 
> Well, GNUS is _very_ old.  It latest version is 4.1 or 4.3 or so.  And
> then, Lars wrote (ding) Gnus which became Gnus 5.0.  There were
> various versions of Gnus 5.x, and as far as I know, the most recent
> versions of Emacs and XEmacs come with Gnus 5.7, whereas the most
> recent version of Gnus is 5.8.  (Maybe XEmacs comes with Gnus 5.6,
> which is more or less the same as 5.7.)

well, I'll contact the XEmacs team about the integration of Gnus 5.8
to XEmacs.

I forgot to ask about pgnus ?

> > well. I'm running XEmacs 21.1 w/ Mule under a FreeBSD box. until the
> > last week, I was running GNUS (Gnus?) featured w/ XEmacs which is
> > version 1.45 from the XEmacs point of view. I upgrade this week end
> > w/ some problem. one of them was that I've apel/flim/semi installed
> > which imply a conflict about the mailcap.el library. XEmacs found
> > the flim one before the gnus one.
> 
> Semi is for dealing with MIME.  As Gnus 5.8 also deals with MIME,
> these two step on each other's toes.  If you want to use Gnus 5.8, you
> must disable Semi and TM and all other packages like it.

for instance, just renaming one of mailcap.el file resolve a major
conflict. as I understood, flim/semi are an evolution of tm, no ?

> (I think it is possible to still use Semi for RMAIL, say, but you must
> disable it for Gnus.)

thanks.

Cyrille.
-- 
home:mailto:clefevre%no-spam@citeweb.net Supprimer "%no-spam" pour me repondre.
work:mailto:Cyrille.Lefevre%no-spam@edf.fr Remove "%no-spam" to answer me back.



  reply	other threads:[~2000-07-11 10:39 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-02 13:12 Lars Magne Ingebrigtsen
2000-07-02 16:08 ` Stainless Steel Rat
2000-07-03 16:37   ` Bug in horizontal recentering (was Re: Gnus v5.8.7 is released) Stainless Steel Rat
2000-07-03 14:22 ` Gnus v5.8.7 is released Thomas Hungenberg
2000-07-11  1:40 ` Cyrille Lefevre
2000-07-11  7:52   ` Kai Großjohann
2000-07-11 10:39     ` Cyrille Lefevre [this message]
2000-07-11 10:54       ` Daniel Pittman
2000-07-11 11:11       ` Kai Großjohann
2000-07-11 18:39         ` Cyrille Lefevre
2000-07-02 19:01 George McNinch
2000-07-02 21:09 ` Kai Großjohann
2000-07-02 21:49   ` George McNinch
2000-07-02 22:01     ` Kai Großjohann
2000-07-02 22:06       ` Kai Großjohann
2000-07-02 22:30 ` ShengHuo ZHU
2000-07-03  5:48   ` John H. Palmieri
2000-07-03 10:26     ` Simon Josefsson
2000-07-03 12:46   ` George McNinch
2000-07-03 14:08     ` Simon Josefsson
2000-07-03 15:01       ` George McNinch
2000-07-03 15:17         ` Kai Großjohann
2000-07-03 15:47           ` Simon Josefsson

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=r991q7b8.fsf@pc166.gits.fr \
    --to=clefevre%no-spam@citeweb.net \
    /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).