From: Brian May <bmay@csse.monash.edu.au>
Subject: Re: Bugs in PGnus
Date: 23 Nov 1999 10:43:29 +1100 [thread overview]
Message-ID: <t4izow6853y.fsf@silas-1.cc.monash.edu.au> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Mon, 22 Nov 1999 10:43:39 +0100"
>>>>> "Kai" == Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> writes:
Kai> Brian May <bmay@csse.monash.edu.au> writes:
>> 1. Pushing A R doesn't retrieve article numbers on my computer
>> at Uni. However it works fine at Home, with the same
>> configuration, except for a different news server (one that I
>> administrate) and a different .newsrc.eld file. (Lars implied
>> that this shouldn't work at all - weird - or perhaps I
>> misunderstood him?). Perhaps the news server here is giving bad
>> index files or something - I don't particularly trust it. It
>> would be good if I could be more specific though, when
>> complaining to the administrator...
Kai> Have you tried setting nntp-record-commands to t, then
Kai> compare traces of the communication between Gnus and the NNTP
Kai> server at uni and at home?
No. Thanks for the suggestion. Will try that and see if anything
obvious shows up...
>> 2. As I already mentioned, threading often has problems, as
>> messages are put with the wrong thread. This seems to be
>> because "Y c" inserts cached articles at the *current* cursor
>> position, and not in thread order. Pushing "T t" on the broken
>> thread fixes it.
>>
>> (I suspect this is only part of the threading problem, but I
>> can reproduce this bug... From memory I get similar problems
>> without pushing "Y c" but haven't yet reproduced it "on
>> demand").
Kai> I also see this problem. Hm. But I use `/ *' rather than `Y
Kai> c'. Is the behavior different? Why are there two commands?
I don't know, I think they are exactly the same thing though...
>From "C-h k Y c":
-------------------------
Y c runs `gnus-summary-insert-cached-articles'
`gnus-summary-insert-cached-articles' is an interactive compiled Lisp function
-- loaded from "gnus-cache.elc"
(gnus-summary-insert-cached-articles)
Insert all the articles cached for this group into the current buffer.
>From "C-h k / *":
-------------------------
/ * runs `gnus-summary-limit-include-cached'
`gnus-summary-limit-include-cached' is an alias for `gnus-summary-insert-cached\
-articles', an interactive compiled Lisp function
-- loaded from "gnus-cache.elc"
(gnus-summary-limit-include-cached)
Insert all the articles cached for this group into the current buffer.
I assume "is an alias for" means that it is exactly the same function,
only with a different name.
>> 3. I get lots of ~/Mail/Incoming* files, which never seem to be
>> deleted. Perhaps this is to keep a backup in case things go
>> wrong, however I already do that via my .forward file.
Kai> See mail-source-delete-incoming. This is indeed a safety net
Kai> because this is an alpha version of Gnus.
Good idea. Only in my case, I already make backup copies via
my .forward file, so this safety net isn't required.
--
Brian May <bmay@csse.monash.edu.au>
next prev parent reply other threads:[~1999-11-22 23:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-22 0:51 Brian May
1999-11-22 2:15 ` Shenghuo ZHU
1999-11-22 2:59 ` Brian May
1999-11-22 3:45 ` Shenghuo ZHU
1999-11-22 9:43 ` Kai Großjohann
1999-11-22 23:43 ` Brian May [this message]
1999-11-23 21:44 ` Kai Großjohann
1999-11-24 23:07 ` Brian May
1999-11-25 9:18 ` Kai Großjohann
1999-11-28 23:39 ` Brian May
1999-11-29 2:46 ` Brian May
1999-12-01 19:16 ` Lars Magne Ingebrigtsen
1999-12-02 1:32 ` Brian May
1999-12-06 4:10 ` Lars Magne Ingebrigtsen
1999-12-06 23:11 ` Brian May
1999-12-07 18:09 ` Shenghuo ZHU
1999-12-01 19:22 ` 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=t4izow6853y.fsf@silas-1.cc.monash.edu.au \
--to=bmay@csse.monash.edu.au \
/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).