From: Bill Gaughan <wgaughan@snet.net>
To: blinux-list@redhat.com
Subject: Re: Mutt or Pine?
Date: Wed, 14 Nov 2001 18:15:21 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.40.0111141812270.386-100000@beethoven.wgaughan.net> (raw)
In-Reply-To: <200111142250.fAEMobK08670@mail.wilnet1.com>
To each his own. That's what makes all this stuff interesting. Pine has no
learning curve and I never use the menus. Just type the letters and go
directly to the place you want to be. For me, command-line stuff is ok,
but, command line options are too much to remember and key-stroke commands
that don't make logical sense are hard to remember too. Why clutter one's
brain with useless info that will change with the next product or version
anyway. I'd rather remember what people say in their e-mails rather than
the command-line options and odd-ball keystrokes I need to decode the
info.
--
Bill Gaughan
wgaughan@snet.net
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <wgaughan@snet.net>
` Christopher Brannon
` Bill Gaughan [this message]
Bill Gaughan
` Henry Yen
` Buddy Brannan
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.0111141812270.386-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).