Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Alexander Glintschert <alexglintschert@netscape.net>
Subject: Re: How to Pine-lize Gnus?
Date: 29 Apr 2002 13:21:16 +0200	[thread overview]
Message-ID: <uofg2lphv.fsf@mail.infopark.de> (raw)
In-Reply-To: <87662btpa4.fsf@enberg.org>

Henrik Enberg <henrik+news@enberg.org> writes:

> Arlan Lucas de Souza <arlan@epsilon.desq.feq.unicamp.br> writes:
> 
> > What's the Pine's secret?
> 
> It is written in C, which is a fast compiled-to-native-code language.
> Gnus is written in Emacs-Lisp which is a slightly less fast bytecompiled
> language.
> 
> Gnus on the other hand has a gazillion more features, and unlike Pine it
> it is free software.

Pine is free software too. Maybe it's not GNU software but you can have the
source code too. And although I think too that Gnus is much better than Pine I
must concede that Pine is easier to use...

Greetings,

        Alex.
-- 
"A good traveller has no fixed plans            Lao Tzu (570-490 BC)
 and is not intent on arriving."
---------------------------------------------------------------------
Alexander Glintschert


           reply	other threads:[~2002-04-29 11:21 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <87662btpa4.fsf@enberg.org>]

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=uofg2lphv.fsf@mail.infopark.de \
    --to=alexglintschert@netscape.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).