public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: Bill Gaughan <wgaughan@snet.net>
To: blinux-list@redhat.com
Subject: Mutt or Pine?
Date: Wed, 14 Nov 2001 15:28:39 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.40.0111141521230.690-100000@beethoven.wgaughan.net> (raw)

Is there really any contest? Let's have a discussion and then let's take a
vote.

You can call lynx from pine when there is a url to be resolved in your
e-mails.

Asking if mutt and pine are equal is sort of like asking if speakup should
replace emacspeak. Any why would you want to use emacs/w3 browser when you
could use lynx or even links. Seriously I have dabbled into all these
products, but, I favor lynx and pine. The url for the "LINKS" web
browser (which shows frames very nicely) is listed below:


http://artax.karlin.mff.cuni.cz/~mikulas/links/



-- 
Bill Gaughan
wgaughan@snet.net





             reply	other threads:[~ UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Bill Gaughan [this message]
 ` Henry Yen
   ` Buddy Brannan
     [not found] <wgaughan@snet.net>
 ` Christopher Brannon
   ` Bill Gaughan

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=Pine.LNX.4.40.0111141521230.690-100000@beethoven.wgaughan.net \
    --to=wgaughan@snet.net \
    --cc=blinux-list@redhat.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).