From: Matthias Andree <matthias.andree@gmx.de>
Cc: Matthias Andree <ma@dt.e-technik.uni-dortmund.de>, ding@gnus.org
Subject: Re: Winbloze Eudora 4 and threading
Date: Fri, 3 Jan 2003 03:02:39 +0100 [thread overview]
Message-ID: <20030103020239.GC4017@merlin.emma.line.org> (raw)
In-Reply-To: <ilulm23ovkf.fsf@latte.josefsson.org>
On Fri, 03 Jan 2003, Simon Josefsson wrote:
> > *sigh* It's always annoying if you're emailing forth and back with a
> > happy Eudora-4 user and then need to get a parent message in a thread
> > that is more than one "hop" away... and the references are
> > missing. Loading enough articles with C-u 200 M-g does the job usually,
> > but it's cumbersome.
>
> Did you try A T?
Didn't always work for me, but I guess that's because I tweaked the
threading options.
--
Matthias Andree
prev parent reply other threads:[~2003-01-03 2:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-09 1:25 Matthias Andree
2002-12-09 2:12 ` Jesper Harder
2002-12-09 14:29 ` Matthias Andree
2002-12-28 18:11 ` Lars Magne Ingebrigtsen
2003-01-02 23:53 ` Matthias Andree
2003-01-03 1:45 ` Simon Josefsson
2003-01-03 2:02 ` Matthias Andree [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=20030103020239.GC4017@merlin.emma.line.org \
--to=matthias.andree@gmx.de \
--cc=ding@gnus.org \
--cc=ma@dt.e-technik.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).