Gnus development mailing list
 help / color / mirror / Atom feed
From: asjo@koldfront.dk (Adam Sjøgren)
Subject: Re: Confusing *Group* after 'gnus-group-jump-to-group' (with topics)
Date: Fri, 14 Apr 2006 19:30:50 +0200	[thread overview]
Message-ID: <87wtdsxdx1.fsf@topper.koldfront.dk> (raw)
In-Reply-To: <m3lku88bt4.fsf@quimbies.gnus.org>

On Fri, 14 Apr 2006 16:35:35 +0200, Lars wrote:

> asjo@koldfront.dk (Adam Sjøgren) writes:
>> (I just tried now, and could here).

> Here's what my group looks like (after I snip all ones below there).

> [ Gnus -- 65441 ]
>       19: nndraft:drafts 
>   [ Stuff -- 3188 ]
>         22: comp.lang.lisp 
> *        0: nnml:misc 
>          2: nnvirtual:emacs 

> `j nntp+news.gmane.org:gmane.culture.sf.delany'

Oh, but the first topic you have after nndraft:drafts must not be
visible when you jump. And the group you jump to must be in that
first, hidden topic.

> Try edebugging `gnus-topic-jump-to-topic' in gnus-topic.el (and
> related functions) to see if you can figure out what's happening. 

I've tried following the path edebug-defun'ing a fun at a time, these
are my notes:

== =
The stuff that goes wrong gets called from:

 gnus-group.el: gnus-group-update-group 1699 - 1716

In line 1703:

  (funcall gnus-goto-missing-group-function group)

calls gnus-topic-goto-missing-group which makes Gnus insert "[0: archive]"
_above_ the  "1: nndraft:drafts"-line.

gnus-topic.el: gnus-topic-goto-missing-group: gnus-topic-display-missing-topic
is called in line 719.

gnus-topic.el: gnus-topic-display-missing-topic calls
gnus-topic-insert-topic-line in line 742-743.

When it does "[0: archive]" is inserted above "1: nndraft:drafts",
which is wrong. Also, "[0: archive]" and "[313: Gnus]" are both
inserted and removed again in to subsequent calls to
gnus-topic-insert-topic-line, for some reason.
== =

It looks like gnus-topic-insert-topic-line inserts the (so far hidden)
"archive" topic directly after its parent-topic "Gnus", instead of
after the groups in "Gnus" that "archive" is usually placed after.

My head is spinning a little now, so I hope someone else can pinpoint
the exact culprit.


  Best regards,

    Adam

-- 
 "You know, if the sun was an oboe, what would you do?"       Adam Sjøgren
                                                         asjo@koldfront.dk




  reply	other threads:[~2006-04-14 17:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-01  9:48 Adam Sjøgren
2006-04-14 13:10 ` Lars Magne Ingebrigtsen
2006-04-14 14:18   ` Adam Sjøgren
2006-04-14 14:35     ` Lars Magne Ingebrigtsen
2006-04-14 17:30       ` Adam Sjøgren [this message]
2006-04-16 16:40         ` Lars Magne Ingebrigtsen
2006-04-16 21:11           ` Adam Sjøgren

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=87wtdsxdx1.fsf@topper.koldfront.dk \
    --to=asjo@koldfront.dk \
    /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).