Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: James Cloos <cloos@jhcloos.com>
Cc: ding@gnus.org
Subject: Re: gnus-group-change-level
Date: Sun, 18 Feb 2024 18:31:57 -0800	[thread overview]
Message-ID: <87il2lmbfm.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <m3sf1pdz23.fsf@nitrogen.jhcloos.org> (James Cloos's message of "Sun, 18 Feb 2024 20:26:28 -0500")

James Cloos <cloos@jhcloos.com> writes:

>>>>>> "EA" == Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
> EA> What is the current level of the group you're trying to change?
>
> I was testing with a switch from 11 to 55 (I have this block in .gnus:
>
>   ;;; use my levels
>   (setq gnus-level-default-subscribed 1)
>   (setq gnus-level-subscribed 80)
>   (setq gnus-level-unsubscribed 90)
>   (setq gnus-level-zombie 98)
>   (setq gnus-level-killed 99)
>   (setq gnus-level-default-unsubscribed 88)
>   (setq gnus-activate-level 80)
>   (setq gnus-activate-foreign-newsgroups 80)

Oh wow, I've never seen anyone do this before. How long has this setup
been functioning? Is your current issue with changing the level of this
group something that's come up recently, and only for this group? If
it's just this one group, and no other groups from this nnimap backend
are behaving this way, can you show me the group parameters for this
group?

> and make significant use of levels for organizing the groups.)
>
>
> Unfortunately adding oldlevel to the tested gnus-group-change-level call
> did not help.

Was oldlevel not set in earlier tests? Oldlevel is retrieved by reading
a text property in the Group buffer -- if you put point where you've had
it in trying to set the level so far, and run M-:
(gnus-group-group-level), what do you get?

> The function succeeded in pulling up the hash and a list along the way,
> it just never changes the group's level.

In current Emacs master, the level should be changed on line 1327:

(setcar (cdadr entry) level)

Do you not reach that line?


  reply	other threads:[~2024-02-19  2:32 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     ` gnus-group-change-level Eric Abrahamsen
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             ` Eric Abrahamsen [this message]
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=87il2lmbfm.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=cloos@jhcloos.com \
    --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).