From: Karl Chen <quarl@nospam.quarl.org>
Subject: Re: smarter nndoc guessing
Date: Thu, 20 May 2004 11:21:37 -0700 [thread overview]
Message-ID: <quack.20040520T1121.j5r7tfufgu@hkn.eecs.berkeley.edu> (raw)
In-Reply-To: <m3vfirqbun.fsf@quimbies.gnus.org>
>>>>> "Lars" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
Lars> If you want mbox interpretation, you can use `C-u C-d',
Lars> I think.
Ok that worked. But I see that as a workaround to a bug. Anyone
that didn't see this post by you wouldn't know what to do except
delete the group and add it again with explicit 'mbox' type.
It's not really ambiguous in the file right?
If it is, I would rather have it err on the side of mbox. So if
you open a single-message-of-multiple-mime-parts, you have to C-u
C-d on that message, rather than the reverse (open an mbox and
have to C-u C-d on the first message to see all messages in a
file)
--
Karl 2004-05-20 11:15
next prev parent reply other threads:[~2004-05-20 18:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-19 9:31 Karl Chen
2004-05-19 23:40 ` Lars Magne Ingebrigtsen
2004-05-20 10:05 ` Karl Chen
2004-05-20 16:53 ` Lars Magne Ingebrigtsen
2004-05-20 18:21 ` Karl Chen [this message]
2004-05-22 23:42 ` Lars Magne Ingebrigtsen
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=quack.20040520T1121.j5r7tfufgu@hkn.eecs.berkeley.edu \
--to=quarl@nospam.quarl.org \
--cc=quarl+dated+1085508904.069259@nospam.quarl.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).