From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: Groups will not stay in topic
Date: Mon, 13 Feb 2023 11:53:50 -0800 [thread overview]
Message-ID: <877cwlfik1.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <877cwosfbx.fsf@yandex.com>
Colin Baxter <m43cap@yandex.com> writes:
> I have several topics, and in my ~/.gnus.el they are arranged according
> to:
>
> (eval-after-load 'gnus-topic
> '(progn
> (setq gnus-topic-topology
> '(("Gnus" visible) ;; root
> (("topic-1" visible nil nil))
> (("topic-2" visible nil nil ))))
> (setq gnus-topic-alist
> '(("topic-1" ; key of first topic
> "group-1"
> "group-2")
> ("topic-2" ; key of second topic
> "group-a"
> "group-b")
> ("Gnus")))))
>
> I have more than two topics and four groups so the above scheme is
> generic only.
>
> Everything works well except for three groups in the final topic. These
> groups will only stay in the topic area during the session in which they
> were placed. In a new gnus session they have jumped out of the topic and
> are visible just below the root "Gnus" but before the first topic. No
> matter how often I return them using "Tm" to the last topic they will
> have jumped out in the next session.
>
> I can live with it, I suppose, but does anyone recognises the issue and
> suggest a solution?
The first and easiest thing to check is if things are going wrong when
.newsrc.eld is being written, or when it's being read. Set your topics
the way you want them, then save and shut down Gnus. Your .newsrc.eld
file will contain a setq form for `gnus-topic-alist', take a look at
that and see if the groups are in the right topic. That will tell us
where to look next.
next prev parent reply other threads:[~2023-02-13 19:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-11 9:48 Colin Baxter
2023-02-13 19:53 ` Eric Abrahamsen [this message]
2023-02-15 20:19 ` Colin Baxter
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=877cwlfik1.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=ding@gnus.org \
/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).