From: Colin Baxter <m43cap@yandex.com>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: ding@gnus.org
Subject: Re: Groups will not stay in topic
Date: Wed, 15 Feb 2023 20:19:31 +0000 [thread overview]
Message-ID: <875yc24r70.fsf@yandex.com> (raw)
In-Reply-To: <877cwlfik1.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Mon, 13 Feb 2023 11:53:50 -0800")
>>>>> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> On 02/14/23 11:06 AM, Colin Baxter wrote:
>> I have discovered that if I look at the Information (GE) for
>> the groups that wont stay in a topic they all begin
>> "nntp+feedbase ..." The well behaved groups don't. And if I
>> move nntp news groups to their own topic they have still jumped
>> out after a new session.
>>
>> I don't understand why the nntp group are different.
> Is the nntp server set as your `gnus-select-method'? Whichever
> server is in there has "unprefixed" group names: everything else
> gets eg nnimap+MyServer:INBOX, but the groups on your primary
> select method don't start with "nntp+feedbase". If that's the
> case, then my guess is that there's some inconsistency somewhere
> between prefixed and unprefixed names: probably you are moving
> prefixed names into the topic, but the next time you start Gnus
> it is using the unprefixed names, so thinks they don't belong to
> that topic.
That looks to be what's happening. The "gnus-secondary-select-methods"
indeed pull in only the nntp+feedbase groups. Thanks to you, at least I
now know the cause of the issue.
Thank you very much.
Best wishes,
Colin Baxter.
prev parent reply other threads:[~2023-02-15 20:19 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
2023-02-15 20:19 ` Colin Baxter [this message]
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=875yc24r70.fsf@yandex.com \
--to=m43cap@yandex.com \
--cc=ding@gnus.org \
--cc=eric@ericabrahamsen.net \
/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).