From: James Cloos <cloos@jhcloos.com>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: ding@gnus.org
Subject: Re: gnus-group-change-level
Date: Sun, 18 Feb 2024 21:58:19 -0500 [thread overview]
Message-ID: <m3jzn1w46s.fsf@nitrogen.jhcloos.org> (raw)
In-Reply-To: <87il2lmbfm.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Sun, 18 Feb 2024 18:31:57 -0800")
>>>>> "EA" == Eric Abrahamsen <eric@ericabrahamsen.net> writes:
EA> Oh wow, I've never seen anyone do this before. How long has this setup
EA> been functioning?
A couple of decades.
EA> Is your current issue with changing the level of this
EA> group something that's come up recently, and only for this group?
I never tried to call gnus-group-change-level directly before, only S L
in the *Groups* buffer, and that as I wrote works fine.
I'm only attempting this because after my previous workstation's
mainboard failed, I ended up using a different imapd on an existing
headless node here. And so the group names have a different hostname.
I want to get the levels back to how I had them on the previous setup,
but w/o manually calling SL thousands of times. Or even just hundreds.
(I used to split some large lists very narrowly; that led to *lots* of
groups. I've chosen not to split them that narrowly this time.)
EA> can you show me the group parameters for this group?
These are the params for nnimap+oxygen:ding@gnus.org:
((modseq . "51")
(uidvalidity . "1689374630")
(active 1 . 24)
(timestamp . 1708309971)
(permanent-flags %Answered %Flagged %Deleted %Seen %Draft %*))
It is at level 11.
EA> Was oldlevel not set in earlier tests?
I used awk to convert a list of '{level} {name}' to a list of
(gnus-group-change-level "nnimap+oxygen:{name}" {level})
where everything outside of {} is static, of course.
EA> if you put point where you've had
EA> it in trying to set the level so far, and run M-:
EA> (gnus-group-group-level), what do you get?
that works.
EA> In current Emacs master, the level should be changed on line 1327:
EA> (setcar (cdadr entry) level)
EA> Do you not reach that line?
I saw that line, but do not recall what edebug showed in the non-working
attempts.
I'll have to re-test. I had to restart gnus in the interim. I'll do
that later tonight.
-JimC
--
James Cloos <cloos@jhcloos.com>
OpenPGP: https://jhcloos.com/0x997A9F17ED7DAEA6.asc
next prev parent reply other threads:[~2024-02-19 4:04 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 ` gnus-group-change-level Eric Abrahamsen
2024-02-19 2:58 ` James Cloos [this message]
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=m3jzn1w46s.fsf@nitrogen.jhcloos.org \
--to=cloos@jhcloos.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).