Gnus development mailing list
 help / color / mirror / Atom feed
From: Kevin Greiner <kgreiner@xpediantsolutions.com>
Subject: Re: PATCH II (for testing only): [Bug, Debian(?)] "g" goes not
Date: Thu, 11 Mar 2004 18:48:57 -0600	[thread overview]
Message-ID: <uk71q28li.fsf@xpediantsolutions.com> (raw)
In-Reply-To: <vita-brevis-breviter-in-brevi-finietur-mors-venit-velociter-quae-neminem-veretur-8765dbovvt.fsf@gothgoose.net>

[-- Attachment #1: Type: text/plain, Size: 744 bytes --]

Marcus Frings <iam-est-hora-surgere@despammed.com> writes:

> * Kevin Greiner <kgreiner@xpediantsolutions.com> wrote:
>
>>> Same results with this patch.  Can I provide more information or help
>>> in some other way?
>
> Well, I'm not Mark but I dare to answer. :-)

Pls do.  I more feedback the sooner this can be put behind us.

>> Definitely.  I'll admit that right now, I'm skeptical that unpatching
>> Lars code change actually fixes this problem.
>
> I promise you: It does! I used 5.10.4 (where it was introduced) with the
> new code: Not working! Then I unpatched 5.10.4 back to the old code:
> It's working!

Alright, let's try one last test concerning Lars patch.  Apply this
patch to the clean (CVS head) revision of gnus-start.el.


[-- Attachment #2: gnus-start.patch2.txt --]
[-- Type: text/plain, Size: 360 bytes --]

--- ../lisp.cvs_ref/gnus-start.el	Tue Mar  9 01:07:19 2004
+++ gnus-start.el	Thu Mar 11 18:41:40 2004
@@ -1673,6 +1673,7 @@
 	       (t
 		'foreign)))
 	(push (cons method method-type) type-cache))
+      (message "Group %s is %s" group method-type)
       (if (and method
 	       (eq method-type 'foreign))
 	  ;; These groups are foreign.  Check the level.

[-- Attachment #3: Type: text/plain, Size: 910 bytes --]


Trigger the bug then look in the *messages* buffer.  Search for one of
the groups that did not update.  Did gnus correctly classify the
group?  What type is this group (i.e. primary, secondary, foreign)?
What type did gnus report?

>> So, here's the next test.  In your group buffer, type
>
>> M-: (gnus-activate-group "GROUP")<RET> {where GROUP is the group name
>>                         as shown in the group buffer.  Obviously pick
>>                         a group that is not updating.}
>
> M-: (gnus-activate-group "INBOX")<RET>
>
>> What does this function return in the minibuffer?  If it is nil, your
>> group isn't activating.
>
> It returns `nil'.

OK, so the actual problem is somewhere inside of
gnus-activate-group (We'll come back to this with the next message).

Here's an interesting test.

Try this
M-x load-library gnus
M-x load-library gnus-start.el
M-x gnus

Has the error gone away?


  reply	other threads:[~2004-03-12  0:48 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-18  1:17 [Bug, Debian(?)] "g" goes not refresh nnimap groups! Marcus Frings
2004-01-18  5:52 ` Simon Josefsson
2004-01-18 22:45   ` Marcus Frings
2004-01-19  6:12     ` Simon Josefsson
2004-01-19 10:30       ` Marcus Frings
2004-02-08 17:21         ` Raymond Scholz
2004-02-08 20:41           ` Marcus Frings
2004-03-04 19:34     ` Marcus Frings
2004-03-04 22:49       ` Simon Josefsson
2004-03-04 23:38         ` Marcus Frings
2004-03-05 20:29           ` Mark Plaksin
2004-03-09  7:02             ` Kevin Greiner
2004-03-09 19:00               ` Marcus Frings
2004-03-09 19:30                 ` Mark Plaksin
2004-03-10  2:25                   ` PATCH (for testing only): " Kevin Greiner
2004-03-10 16:45                     ` PATCH (for testing only): [Bug, Debian(?)] "g" goes not refresh Mark Plaksin
2004-03-10 18:58                       ` PATCH II (for testing only): [Bug, Debian(?)] "g" goes not Kevin Greiner
2004-03-10 19:38                         ` Mark Plaksin
2004-03-10 22:36                         ` Marcus Frings
2004-03-11  0:10                         ` Kevin Greiner
2004-03-11 22:35                         ` Marcus Frings
2004-03-12  0:48                           ` Kevin Greiner [this message]
2004-03-13 22:13                           ` Marcus Frings
2004-03-12  1:04                         ` Mark Plaksin
2004-03-12  3:42                         ` Mark Plaksin
2004-03-12  6:40                         ` Kevin Greiner
2004-03-12 12:37                         ` Marcus Frings
2004-03-13 15:23                         ` Mark Plaksin
2004-03-13 20:22                         ` Marcus Frings
2004-03-13 23:10                         ` Marcus Frings
     [not found]                         ` <m38yi87ar9.fsf@ <m3brn0db3t.fsf@water.tss.usg.edu>
2004-03-14  7:17                           ` Kevin Greiner
2004-03-14 13:16                           ` Marcus Frings
     [not found]                           ` <v <vita-brevis-breviter-in-brevi-finietur-mors-venit-velociter-quae-neminem-veretur-87d67fpo0n.fsf@gothgoose.net>
2004-03-14 13:27                             ` Mark Plaksin
2004-03-16  3:38                               ` Kevin Greiner
2004-03-21 17:44                               ` Marcus Frings
     [not found]                               ` <vita-brevis-breviter-in-brevi-finietur-mors-venit-velociter-quae-neminem-ve <ud67dea0u.fsf@xpediantsolutions.com>
2004-03-23  1:30                                 ` Kevin Greiner
2004-03-23 20:37                                 ` Marcus Frings
2004-04-17 16:09                                 ` Marcus Frings
     [not found]                                 ` <vita-brevis-breviter-in-brevi-finietur-mors-venit-velociter-quae-neminem-veretur-87brmqdri1.fsf@gothgoose.net <u3c80e4ex.fsf@xpediantsolutions.com>
2004-04-18 20:29                                   ` Kevin Greiner
2004-04-27 12:25                                   ` Marcus Frings
2004-03-14 14:12                             ` Marcus Frings
2004-03-10 22:08                     ` PATCH (for testing only): [Bug, Debian(?)] "g" goes not refresh Marcus Frings

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=uk71q28li.fsf@xpediantsolutions.com \
    --to=kgreiner@xpediantsolutions.com \
    /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).