From: Peter Davis <pfd@pfdstudio.com>
To: ding@gnus.org
Subject: Re: fetching old headers
Date: Wed, 28 Jan 2015 18:48:57 -0500 [thread overview]
Message-ID: <m2k306jwk6.fsf@PFDStudio-Air.home> (raw)
In-Reply-To: <m2egqhlmc3.fsf@PFDStudio-Air.home> (Peter Davis's message of "Mon, 26 Jan 2015 08:10:04 -0500")
Peter Davis <pfd@pfdstudio.com> writes:
> Lars Ingebrigtsen <larsi@gnus.org> writes:
>
>> Peter Davis <pfd@pfdstudio.com> writes:
>>
>>> I'm using gnus v5.13 on 3 different Macs, all using the same .gnus.el
>>> file. On all three, gnus-fetch-old-headers is set to t. Also, they're
>>> all reading via nnimap from the same IMAP server.
>>>
>>> Yet the gnus-fetch-old-headers only seems to work on one of them. I only
>>> see earlier messages in the thread, marked with O, on one machine.
>>>
>>> Is there something else, some other variable or state, that could affect
>>> this behavior?
>>
>> Are you using the same Emacs version on all three machines? And are you
>> using the Agent?
>
> Evidently not (though I thought I was.) The one that's showing old
> headers is running
> Aquamacs 3.2 GNU Emacs 24.4.51.2,
> but the other two are running
> Aquamacs 3.0 GNU Emacs 24.3.50.2
>
> So maybe that's it. I'll try upgrading the other machines.
Well, I've upgraded one of the other ones to Aquamacs 3.2 GNU Emacs
24.4.51.2, but I'm still not getting old headers.
> As for Agent, I'm not working offline, so I thought that was not
> relevant.
Is this apt to make a difference? I don't know anything about Agent, or
what to do with it.
Thanks,
-pd
next prev parent reply other threads:[~2015-01-28 23:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-21 19:42 Peter Davis
2015-01-26 4:45 ` Lars Ingebrigtsen
2015-01-26 13:10 ` Peter Davis
2015-01-28 23:48 ` Peter Davis [this message]
2015-01-29 1:35 ` Lars Ingebrigtsen
2015-01-29 1:44 ` Peter Davis
2015-01-29 2:34 ` Lars 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=m2k306jwk6.fsf@PFDStudio-Air.home \
--to=pfd@pfdstudio.com \
--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).