From: Kai Grossjohann <grossjoh@charly.informatik.uni-dortmund.de>
Subject: sgnus-0.38 and M-g
Date: 14 Feb 1996 17:47:34 +0100 [thread overview]
Message-ID: <vafohr1c0rd.fsf@dusty.informatik.uni-dortmund.de> (raw)
nnmail-split-methods is '(("mail.misc" "")). nnml:mail.misc is the
only group that's on level 1, all other nnml groups are level 2, and
nntp groups are level 3. nnml-spool-file is
'("/home/crew/grossjoh/spool/incoming/outgoing"
"/home/crew/grossjoh/spool/incoming/lists"
"/var/spool/mail/grossjoh").
I'm in the nnml:mail.misc summary buffer, and there is new mail in an
nnmail-spool-file. I hit M-g.
sgnus does not read any nnmail-spool-file and it does not put the
messages into nnml:mail.misc. Why not?
I'm in the *Group* buffer. I hit `1 g'. Still no joy: no mail is
being read from nnmail-spool-file.
I'm in the *Group* buffer with point on nnml:mail.misc. I hit M-g.
Still no joy :-(
Is this a feature or is it a bug? I know that I've asked for
something like this but that was different.
Old behavior:
Hitting M-g in an nnml group would read the procmail spool file for
that group, plus nnmail-spool-file. This was true for any
nnml group, not just nnml:mail.misc. Thus, hitting M-g in nnml:foo
would put all messages from nnmail-spool-file into nnml:foo.
This is okay if foo equals mail.misc but undesirable else.
New behavior:
Hitting M-g in an nnml group reads the procmail spool file and under
no circumstances reads nnmail-spool-file.
Desired behavior:
Hitting M-g in any nnml group *except* nnml:mail.misc reads the
procmail spool file and nothing else. Hitting M-g in nnml:mail.misc
reads the procmail spool file, plus nnmail-spool-file. Here,
messages from the procmail spool file are put into nnml:mail.misc;
but messages from nnmail-spool-file are put through the normal
splitting process, as always.
Maybe M-g should always read nnmail-spool-file (in addition to the
procmail spool file) and put the messages through the normal
splitting process, not only for nnml:mail.misc?
Did I express myself clearly enough, do you understand?
What do you all think?
kai
--
Life is hard and then you die.
reply other threads:[~1996-02-14 16:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=vafohr1c0rd.fsf@dusty.informatik.uni-dortmund.de \
--to=grossjoh@charly.informatik.uni-dortmund.de \
/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).