From: Reiner Steib <reinersteib+gmane@imap.cc>
To: Leo <sdl.web@gmail.com>
Cc: emacs-pretest-bug@gnu.org, Gnus <ding@gnus.org>
Subject: Re: A bug in doc string of `gnus-level-unsubscribed'?
Date: Mon, 11 Jun 2007 19:37:20 +0200 [thread overview]
Message-ID: <v98xaqie9b.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <m2ir9usdxt.fsf@sl392.st-edmunds.cam.ac.uk> (Leo's message of "Mon, 11 Jun 2007 16:34:06 +0100")
[ Please report Gnus issues directly to the Gnus list ding@gnus.org,
or at least Cc ding ]
On Mon, Jun 11 2007, Leo wrote:
> ,----
> | gnus-level-unsubscribed is a variable defined in `gnus-start.el'.
> | Its value is 7
> |
> |
> | Documentation:
> | Groups with levels less than or equal to this variable are unsubscribed.
> | Groups with levels less than `gnus-level-subscribed', which should be
> | less than this variable, are subscribed.
> `----
>
> The first 'less' should be 'more', right?
No, see (info "(gnus)Group Levels"). Is the following doc string more
clear?
,----[ <f1> v gnus-level-unsubscribed RET ]
| gnus-level-unsubscribed is a variable defined in `gnus-start.el'.
| Its value is 7
|
|
| Documentation:
| Groups with levels less than or equal to this variable are
| unsubscribed. Groups with levels less than `gnus-level-subscribed',
| which should be less than this variable, are subscribed. Groups
| with levels from `gnus-level-subscribed' (exclusive) upto this
| variable (inclusive) are unsubscribed. See also
| `gnus-level-zombie', `gnus-level-killed' and the Info node `Group
| Levels' for details.
`----
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next parent reply other threads:[~2007-06-11 17:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m2ir9usdxt.fsf@sl392.st-edmunds.cam.ac.uk>
2007-06-11 17:37 ` Reiner Steib [this message]
2007-06-11 21:52 ` Leo
2007-07-02 19:07 ` Reiner Steib
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=v98xaqie9b.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--cc=ding@gnus.org \
--cc=emacs-pretest-bug@gnu.org \
--cc=sdl.web@gmail.com \
/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).