a...@koldfront.dk (Adam Sjøgren) writes:
> Andreas writes:
>
>> Adam Sjøgren koldfront.dk> writes:
>>
>>> Ah! This looks suspicious:
>>>
>>> gnus-fetch-old-headers t
>>>
>>> From the documentation:
>>>
>>> "This feature can seriously impact performance it ignores all locally
>>> cached
Hi,
I am sorry.
>> and the C-h v gnus-fetch-old-headers value is nil
^ ^^^ This was from my
box at home! and the one that misbehaved was the one that was
at workplace. And indeed it had the same configuration error
The
B.V. writes:
>>> and the C-h v gnus-fetch-old-headers value is nil
>^ ^^^ This was from my
>box at home! and the one that misbehaved was the one that was
>at workplace. And indeed it had the same configuration error
Ah, ok,
Andreas writes:
>> How many articles do you ask Gnus to display when entering a group?
> 200
I think it should only fetch the "overview" for the newest 200 then. Odd.
>> Have you "caught up" the groups in question (i.e. marked all the old
>> articles as read)?
> Yes, the *group* buffer shows
Andreas writes:
> Adam Sjøgren koldfront.dk> writes:
>
>> Ah! This looks suspicious:
>>
>> gnus-fetch-old-headers t
>>
>> From the documentation:
>>
>> "This feature can seriously impact performance it ignores all locally
>> cached header entries. Setting it to t for groups for a server
Hi,
>>> Ah! This looks suspicious:
>>>
>>> gnus-fetch-old-headers t
I run:
GNU Emacs 24.5.1 (x86_64-pc-linux-gnu, X toolkit, Xaw3d scroll bars) of
2015-10-25 on trouble, modified by Debian
and the C-h v gnus-fetch-old-headers value is nil
I have a little different issue. When I subscribe
B.V. writes:
> and the C-h v gnus-fetch-old-headers value is nil
>
> I have a little different issue. When I subscribe to a group like
> debian.user -- The history is pretty large, 150MB or so. I had marked it
> read by using `c' key to catch-up the group.
>
> However, now when entering the
Adam Sjøgren koldfront.dk> writes:
> Ah! This looks suspicious:
>
> gnus-fetch-old-headers t
>
> From the documentation:
>
> "This feature can seriously impact performance it ignores all locally
> cached header entries. Setting it to t for groups for a server that
> doesn't expire
a...@koldfront.dk (Adam Sjøgren) writes:
> Andreas writes:
>
>> I'd like to start using GNUs to read mailing lists via nntp/Gmane. Works
>> fine so far, but each time I press RET on a group name in the *Group*
>> buffer, GNUs seems to download a lot of data (in case of the org-mode
>> list, some
Andreas Hilboll writes:
> a...@koldfront.dk (Adam Sjøgren) writes:
>
>> Andreas writes:
>>
>>> I'd like to start using GNUs to read mailing lists via nntp/Gmane. Works
>>> fine so far, but each time I press RET on a group name in the *Group*
>>> buffer, GNUs seems to
Andreas writes:
> I'd like to start using GNUs to read mailing lists via nntp/Gmane. Works
> fine so far, but each time I press RET on a group name in the *Group*
> buffer, GNUs seems to download a lot of data (in case of the org-mode
> list, some 30+M, which takes 10+ seconds).
Sounds strange,
Hello,
I'd like to start using GNUs to read mailing lists via nntp/Gmane. Works
fine so far, but each time I press RET on a group name in the *Group*
buffer, GNUs seems to download a lot of data (in case of the org-mode
list, some 30+M, which takes 10+ seconds).
Maybe I don't understand the
12 matches
Mail list logo