Gnus development mailing list
 help / color / mirror / Atom feed
From: James Cloos <cloos@jhcloos.com>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: ding@gnus.org
Subject: Re: gnus-group-change-level
Date: Tue, 20 Feb 2024 11:18:04 -0500	[thread overview]
Message-ID: <m38r3fcdoj.fsf@nitrogen.jhcloos.org> (raw)
In-Reply-To: <875xyjlmqz.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Mon, 19 Feb 2024 21:37:24 -0800")

>>>>> "EA" == Eric Abrahamsen <eric@ericabrahamsen.net> writes:

EA> (let ((level 55))
EA>   (dolist (grp very-long-list-of-group-names)
EA>     (when-let ((entry (gnus-group-entry grp)))
EA>       (setcar (cdadr entry) level))))

Ah.  Cool.  As a first step I tried out:

 (cdadr (gnus-group-entry "nnimap+oxygen:ding@gnus.org"))

since ding was at point and thus easy to copy-n-yank.

It errored out that (listp 0) return nil.

Some experimentation showed that:

 (cadadr (gnus-group-entry "nnimap+oxygen:ding@gnus.org"))

returned the cons (11 . 15), where 11 is the current level.
(I'm not sure what that cons' cdr is.)

I see aroung 7% of the groups' lines in .newsrc.eld have just an integer
at that point for level, whereas the others have such a cons.

Eg this returns just the integer 11:

 (cadadr (gnus-group-entry "nnimap+oxygen:GitHub-Torvalds"))

I take it setcar will not do the right thing in such cases, yes?
And something like a cl-typecase would be required?

Is cadadr setf-able in emacs?

Thanks for the help!

P.S.  setting (nnimap-expunge never) or (nnimap-expunge 'never)
      in an entry in gnus-secondary-select-methods doesn't seem
      to do anything.  dovecot removes the files everytime gnus
      quits the *Summary* buffer.  I want to set \Delete but not
      to expunge...

-JimC
-- 
James Cloos <cloos@jhcloos.com>
            OpenPGP: https://jhcloos.com/0x997A9F17ED7DAEA6.asc



  reply	other threads:[~2024-02-20 16:18 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               ` gnus-group-change-level James Cloos
2024-02-20  5:37                 ` gnus-group-change-level Eric Abrahamsen
2024-02-20 16:18                   ` James Cloos [this message]
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=m38r3fcdoj.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).