Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: ding@gnus.org
Subject: Re: gnus-group-change-level
Date: Thu, 22 Feb 2024 18:08:02 -0800	[thread overview]
Message-ID: <875xyggcfx.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87cysssovx.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Mon, 19 Feb 2024 10:57:06 +0000")

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> On Sunday, 18 Feb 2024 at 20:26, James Cloos wrote:
>> I was testing with a switch from 11 to 55 (I have this block in .gnus:
>
> [...]
>
>> and make significant use of levels for organizing the groups.)
>
> Thank you for this.  Some time ago, I tried changing from the 1-5 levels
> that is the gnus default and ended up with a totally confused system,
> probably because I missed some of the variables I needed to set.  So I
> will now try with your list of variables to see how it goes.  I don't
> need 100 group levels but 10 or so would be nice.

Part of the reason I was surprised here is that the various
`gnus-level-*' variables, far from being user options, are actually
defined with `defconst', which would indicate that Gnus didn't want you
fooling with them. It's possible that was done so that the variables are
marked as "special", but defcustom would have the same effect.

Anyway, it's encouraging to know that it's been working correctly for
some people for a while.


      reply	other threads:[~2024-02-23  2:08 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                   ` 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               ` Eric Abrahamsen [this message]

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=875xyggcfx.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=ding@gnus.org \
    --cc=e.fraga@ucl.ac.uk \
    /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).