From: Wes Hardaker <wes@hardakers.net>
To: David <de_bb@arcor.de>
Cc: ding@gnus.org
Subject: Re: nnmairix bug report
Date: Thu, 28 Feb 2008 14:51:06 -0800 [thread overview]
Message-ID: <sdtzjsvgo5.fsf@wes.hardakers.net> (raw)
In-Reply-To: <kzskzcivyn.fsf@kafka.physik3.gwdg.de> (David's message of "Thu, 28 Feb 2008 22:59:12 +0100")
>>>>> "D" == David <de_bb@arcor.de> writes:
D> What mail spool format are you using with UW IMAP, mbox or mh?
mbox...
I'll look into more debugging when I get a chance in the next few days.
D> By the way, I tried to reproduce your problems with Xemacs and
D> gnus-thread-sort-by-most-recent-number, but couldn't see any difference
D> when nnmairix was loaded. If you can somehow narrow down the problem,
D> please let me know.
I'm not shocked... My system is a bit, as I mentioned, over-customized
(which is why I can never move away from it).
--
"In the bathtub of history the truth is harder to hold than the soap,
and much more difficult to find." -- Terry Pratchett
prev parent reply other threads:[~2008-02-28 22:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 21:05 Wes Hardaker
2008-02-28 21:59 ` David
2008-02-28 22:51 ` Wes Hardaker [this message]
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=sdtzjsvgo5.fsf@wes.hardakers.net \
--to=wes@hardakers.net \
--cc=de_bb@arcor.de \
--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).