Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: jesse@phiwumbda.org (Jesse F. Hughes)
Subject: Do Pine and Gnus play well together?
Date: Fri, 11 Jun 2004 18:56:05 +0200	[thread overview]
Message-ID: <873c528256.fsf@phiwumbda.org> (raw)

Hey ho.

I am a long time Gnus user, but my wife prefers Pine so far.  She
likes its simplicity (even though she is fairly well acquainted with
xemacs).

However, she's jealous of my ability to search my emails for text
excerpts (via nnir) and so she's thinking of switching to Gnus.

Now, here are the problems:  

(1) She uses imap and isn't likely to change.  As I understand it,
that still allows for nnir, but it's much slower than using eswish
locally, like I do.

(2) She is not sure she wants to permanently give up Pine.  She might
want to use Pine when she's stuck on a Windows machine and has to ssh.
She has this odd aversion to text-only xemacs -- a sad dependence on
menus, I'm told.  Also, she might just not like Gnus (perish the
thought) and might want to switch back.

Are there any strategies well-suited for a Pine user (with tons of
folders of saved mail) to use Gnus on an experimental basis?  Let's
assume she's a true agnostic and that each time she chooses to read
mail, a coin is flipped to determine which program is used.  Any
tricks to make this as painless as possible?

Thanks much.

-- 
"Sure, [my Usenet presence is] like Shaq playing against you in your
backyard, but that has its perks, as I find ways to have my fun *and*
I can send messages to certain people in the United States Government
without concern that the rest of you understand them." -- James Harris


             reply	other threads:[~2004-06-11 16:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-11 16:56 Jesse F. Hughes [this message]
2004-06-11 17:11 ` 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=873c528256.fsf@phiwumbda.org \
    --to=jesse@phiwumbda.org \
    /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).