From: dsg@mitre.org (David S. Goldberg)
Subject: Re: has "incorporating new mail" bug been fixed yet?
Date: 23 Dec 1999 13:23:44 -0500 [thread overview]
Message-ID: <m1br9gdwm6n.fsf@blackbird.mitre.org> (raw)
In-Reply-To: merlyn@stonehenge.com's message of "23 Dec 1999 09:51:59 -0800"
> So where are we at? Did the latest release fix it so that I can:
> M-g on a single nnml group
Yes.
> 2 M-g to get all nnml groups at level 2-1
Yes.
> gnus-no-server to start at my level 2-1 groups
Yes.
> without the annoying dozens of "no mail" messages?
No :-(
My workaround: nnml incorporation works without all the "no mail"
messages if you run gnus and use 'g'. In fact, I've found that to be
so fast now that I don't mind the connection to my primary nntp
server. Of course that nntp server is only three hops away on a
mostly 100baseT switched network. I've added this advice
(defadvice gnus-group-list-groups (around set-default-list-level activate)
ad-do-it
(if (ad-get-arg 0) (setq gnus-group-default-list-level (ad-get-arg 0))))
to ensure that when I do a '2 l' (or '1 l') only the groups on that
level are displayed and subsequent calls to 'l' don't bring in all the
higher ones.
I don't fully understand the lisp needed to fix this. I *think* that
nnml-request-scan (and probably others, too) needs to be made
specifically aware of a directory mail-source but I haven't had time
to try to actually write code to make it do so.
--
Dave Goldberg
Post: The Mitre Corporation\MS B325\202 Burlington Rd.\Bedford, MA 01730
Phone: 781-271-3887
Email: dsg@mitre.org
next prev parent reply other threads:[~1999-12-23 18:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-23 17:51 Randal L. Schwartz
1999-12-23 18:23 ` David S. Goldberg [this message]
1999-12-23 20:16 ` Randal L. Schwartz
1999-12-23 18:39 ` Bud Rogers
1999-12-23 20:18 ` Randal L. Schwartz
1999-12-23 20:39 ` Bud Rogers
1999-12-23 20:39 ` David S. Goldberg
1999-12-24 6:15 ` Randal L. Schwartz
1999-12-24 23:46 ` 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=m1br9gdwm6n.fsf@blackbird.mitre.org \
--to=dsg@mitre.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).