From: Chris Uzdavinis <chris@atdesk.com>
Cc: ding@gnus.org
Subject: Re: Gnus status
Date: Tue, 10 Jun 2003 08:19:33 -0400 [thread overview]
Message-ID: <j6u1ayunu2.fsf@explicit.atdesk.com> (raw)
In-Reply-To: <87smqj3yix.fsf@windlord.stanford.edu> (Russ Allbery's message of "Mon, 09 Jun 2003 11:18:30 -0700")
Russ Allbery <rra@stanford.edu> writes:
> Chris Uzdavinis <chris@atdesk.com> writes:
>
>> Hi, I've been a happy user of Gnus 5.8.8 for a while and am considering
>> moving up to a newer version, but I'm wondering what your thoughts are
>> on using the latest it as a primary mail client. Do you consider it
>> ready for "real" use, or does it still at the stage where it
>> "occationally rains down death and destruction on innocent bystanders"?
>
> I'm using Gnus 5.10.2 as my primary mail client, and was using Oort
> development releases before that. I've not had any problems.
Thanks for your feedback, and also to Nevin.
I've updated to 5.10.2 and so far it has been drop-in compatible with
the old version. I haven't made any changes to my .gnus file but it
all seems to be working just the same (though I haven't tried
newsgroups yet, just mail.) I'm not used to updates being so easy.
:)
I notice a few changes already, like something called "queue" appears
in the Group buffer. Also there is a dot to the left of each piece of
mail in the summary buffer. These types of things probably are neat
new features, but I'm not sure what they mean. I guess I have some
reading to do.
--
Chris
next prev parent reply other threads:[~2003-06-10 12:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-09 15:28 Chris Uzdavinis
2003-06-09 16:19 ` Nevin Kapur
2003-07-08 5:03 ` Karl Eichwalder
2003-06-09 18:18 ` Russ Allbery
2003-06-10 12:19 ` Chris Uzdavinis [this message]
2003-06-10 16:54 ` Kai Großjohann
2003-06-11 5:29 ` Xavier Maillard
2003-06-12 20:52 ` Chris Uzdavinis
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=j6u1ayunu2.fsf@explicit.atdesk.com \
--to=chris@atdesk.com \
--cc=ding@gnus.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).