Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: gnus-group-change-level
Date: Sun, 18 Feb 2024 09:46:48 -0800	[thread overview]
Message-ID: <87ttm5psvr.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <m3wmr55znj.fsf@nitrogen.jhcloos.org>

James Cloos <cloos@jhcloos.com> writes:

>>>>>> "AS" == Andreas Schwab <schwab@linux-m68k.org> writes:
>
> AS> On Feb 14 2024, James Cloos wrote:
>>> Eg, this just returns nil w/o changing the level:
>>> 
>>> (gnus-group-change-level "nnimap+oxygen:INBOX" 6)
>>> 
>>> even though nnimap+oxygen13:INBOX
>
> AS> There is a discrepancy between the two names.  Typo?
>
> yes.  the typo is only in the email.

I think you would need to edebug `gnus-group-change-level' and see
what's happening. That function uses `gnus-group-entry' to turn the
group string name into a group data structure, but all that macro does
is `gethash' on the `gnus-newsrc-hashtb', and you've already stated that
this works:

(gethash "nnimap+oxygen:INBOX" gnus-newsrc-hashtb)

so it looks like the function should at least be finding your group
correctly, and things are going wrong elsewhere. Are you comfortable
using edebug?

Eric



  reply	other threads:[~2024-02-18 17:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-15  3:20 gnus-group-change-level James Cloos
2024-02-15 18:41 ` gnus-group-change-level Andreas Schwab
2024-02-15 18:51   ` gnus-group-change-level James Cloos
2024-02-18 17:46     ` Eric Abrahamsen [this message]
2024-02-18 19:47       ` gnus-group-change-level James Cloos
2024-02-18 20:02       ` gnus-group-change-level James Cloos
2024-02-18 20:07         ` gnus-group-change-level Eric Abrahamsen
2024-02-19  1:26           ` gnus-group-change-level James Cloos
2024-02-19  2:31             ` gnus-group-change-level Eric Abrahamsen
2024-02-19  2:58               ` gnus-group-change-level James Cloos
2024-02-20  5:37                 ` gnus-group-change-level Eric Abrahamsen
2024-02-20 16:18                   ` gnus-group-change-level James Cloos
2024-02-22 17:13                     ` gnus-group-change-level Eric Abrahamsen
2024-02-22 18:39                       ` gnus-group-change-level Andreas Schwab
2024-02-22 22:00                         ` gnus-group-change-level Eric Abrahamsen
2024-02-22 22:36                       ` gnus-group-change-level James Cloos
2024-02-19 10:57             ` gnus-group-change-level Eric S Fraga
2024-02-23  2:08               ` gnus-group-change-level Eric Abrahamsen

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=87ttm5psvr.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).