From: "jim grimsby" <jimgrims@pacbell.net>
To: "Speak Up Mailing List" <speakup@braille.uwo.ca>
Subject: Mutt or pine and best configuration to use?
Date: Sat, 2 Apr 2005 02:26:43 -0800 [thread overview]
Message-ID: <000001c5376e$78b204f0$220110ac@jim> (raw)
Hi, well the subject says what I am looking for. I have looked at the
man pages for both mutt and pine. I also have played with fetch mail
and mutt a little. I have to say I like it but pine sounds a little
more user friendly from what I have read. So just wondering what do
most of you guys use mutt or pine. Advantages and disadvantages. Also
I remember some one saying there are some things that should be changed
for mutt and pine to make them work better using speakup. I have looked
threw the manuals and see nothing witch advices about this. Now if
these questions have already been answered before and if I am generating
list clutter I am sorry. If that is the case please direct me to where
I can look to find out about these things and I will leave the list
alone. Thanks
next reply other threads:[~ UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
jim grimsby [this message]
` Luke Yelavich
` Kenny Hitt
` Luke Yelavich
` David Csercsics
` Kenny Hitt
` Janina Sajka
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='000001c5376e$78b204f0$220110ac@jim' \
--to=jimgrims@pacbell.net \
--cc=speakup@braille.uwo.ca \
/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).