From: Emerick Rogul <emerick@cs.bu.edu>
Subject: Re: Bug when jumping to group in empty topic?
Date: Tue, 21 Jan 2003 07:58:09 -0500 [thread overview]
Message-ID: <vuo3cnmd5i6.fsf@csa.bu.edu> (raw)
In-Reply-To: <m38yxfqco0.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Tue, 21 Jan 2003 06:45:03 +0100")
Lars Magne Ingebrigtsen writes:
> I'm unable to reproduce this -- when I jump to a group in an
> undisplayed topic, the topic inserted in the right place. There's
> probably some subtlety in `gnus-topic-goto-missing-topic' where it
> puts point at the wrong place somewhere. Try edebug-defun on that
> function and eval `(gnus-topic-goto-missing-topic "old")'.
I just noticed that it also seems to be affected by the fact that I
have the following in my .gnus.el:
;; always display these groups in the group buffer.
(setq gnus-permanently-visible-groups "^nn\\(dir\\|doc\\|folder\\)")
When I comment out that line, gnus inserts the topic in the correct
place when I hit 'j'.
So the way to reproduce this seems to be:
1) Set gnus-permanently-visible-groups as shown above.
2) Set gnus-display-empty-topics to nil.
3) 'j' to a hidden group (the group probably needs to use one of the
backends specified in gnus-permanently-visible-groups - I use an
nnfolder group).
Does that reproduce the problem for you?
-Emerick
--
-------------------------------------------------------------------------
Emerick Rogul /\/ "how young are you, how old am i?
emerick@cs.bu.edu /\/ let's count the rings around my eyes."
------------------------------------------------- 'i will dare', the mats
next prev parent reply other threads:[~2003-01-21 12:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-13 19:05 Emerick Rogul
2003-01-21 5:45 ` Lars Magne Ingebrigtsen
2003-01-21 12:58 ` Emerick Rogul [this message]
2003-01-24 21:12 ` Lars Magne Ingebrigtsen
2003-01-24 21:47 ` Emerick Rogul
2003-02-07 13:29 ` Lars Magne Ingebrigtsen
2003-02-07 19:59 ` Emerick Rogul
2003-02-09 0:00 ` 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=vuo3cnmd5i6.fsf@csa.bu.edu \
--to=emerick@cs.bu.edu \
/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).