Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: kai.grossjohann@uni-duisburg.de (Kai Großjohann)
Subject: Re: nnmail-split-fancy-with-parent problem
Date: Tue, 04 Mar 2003 12:12:06 +0100	[thread overview]
Message-ID: <84el5nwfll.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: <m31y1n8mij.fsf@wilson.rwth-aachen.de>

Torsten Bronger <bronger@physik.rwth-aachen.de> writes:

> I created a new .nnmail-cache file; 582 lines in the original (i.e. all lines
> without a group name) were deleted.  As a result, everything works fine.  So
> nnmail-split-fancy-with-parent is not the problem, however Gnus still creates
> two of such lines for every outgoing message.

It is normal to have lines without a group name: those are created
when Gnus does not know the group.

*Please* debug this.  You could do a lot of people a great favor.  I
don't have the time to debug it myself.
-- 
A preposition is not a good thing to end a sentence with.


           reply	other threads:[~2003-03-04 11:12 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <m31y1n8mij.fsf@wilson.rwth-aachen.de>]

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=84el5nwfll.fsf@lucy.is.informatik.uni-duisburg.de \
    --to=kai.grossjohann@uni-duisburg.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).