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: Sun, 18 Feb 2024 14:47:30 -0500	[thread overview]
Message-ID: <m3plwt367h.fsf@nitrogen.jhcloos.org> (raw)
In-Reply-To: <87ttm5psvr.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Sun, 18 Feb 2024 09:46:48 -0800")

I stepped thru gnus-group-change-level w/ edebug.

I did not spot anything obvious.  The steps converting the string all
looked correct.  The final nil return looks to be due to not having a
gnus-group-change-level-function configured, and thus innocuous.

But at least on the first step-thru I didn't see why the level does
not get changed.

I'll have to step thru when it is called via the *Groups* buffer UI
and see what is different.

(I'm currently running gnus on 29 rather than master, if it makes a
difference.  Master's font support was horibly screwed up when I last
tried using it for gnus.  Glyphs were changing their font while I was
reading the article and junk like that.  Plus it was ignoring my font
choices and choosing random fonts behind my back.  29 isn't doing so.)

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


  reply	other threads:[~2024-02-18 19:47 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       ` James Cloos [this message]
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=m3plwt367h.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).