minor nit with pgnus mail-fetching

[Justin Sheehy <dworkin@ccs.neu.edu>]

I've probably explained my mail-handling process here before a couple
of times, but I'll do so again for background.

I filter via procmail into spools in ~/Mail/incoming, one per nnml
group.  For various reasons, this suits my needs better than using
Gnus splitting.

One thing that I do quite frequently is M-g over a given mail group.
An advantage of my mail setup in this situation is that it does not
have to process any mail for groups other than the one I am interested 
in.

My nnmail-spool-file is   `((directory :path 
                             ,(expand-file-name "~/Mail/incoming")
                             :suffix ""))

If I M-g over a group that does have new mail, Gnus acts as expected:

nnml: Reading incoming mail from directory...
Wrote blah/blah/43
Wrote blah/blah/44
Wrote blah/blah/45
nnml: Reading incoming mail (3 new)...done

However, if I M-g over a group with no new mail, Gnus simply says:

nnml: Reading incoming mail from directory... 

and never says "done" or "no news" or even erases the message.  Thus,
one does not immediately know if it is taking Gnus a long time to
access the file or if there is in fact no mail there.

This is suboptimal behavior.  I've taken a quick look at the relevant
code, but I do not have the time to invesitgate as deeply as I would like.

-Justin