From: Richmond <dnomhcir@gmx.com>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: info-gnus-english@gnu.org
Subject: Re: Gnus Describe Group and Gnus Describe All Groups
Date: Sun, 16 Feb 2020 15:58:58 +0000 [thread overview]
Message-ID: <34275.7378633664$1581868764@news.gmane.org> (raw)
In-Reply-To: <87eeuvqjgp.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Sat, 15 Feb 2020 19:50:14 -0800")
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> Richmond <dnomhcir@gmx.com> writes:
>
>> Eric Abrahamsen wrote:
>>> Richmond <dnomhcir@gmx.com> writes:
>>>
>>>> When viewing the list of subscribed groups in gnus, you can select
>>>> from
>>>> the group menu an option to describe the group (ctrl-c ctrl-d). For
>>>> this
>>>> group the description is "News reading under GNU Emacs using GNUS
>>>> (in
>>>> English)." There is also an option to describe all groups (alt-d
>>>> or
>>>> M-d). I anticipated that this would put the description like
>>>> above
>>>> beside each group, but it just puts the group name. Is this a
>>>> bug?
>>> When I run `gnus-group-describe-all-groups' it pops up a completely
>>> separate buffer containing all group descriptions, one per line.
>>> `gnus-group-describe-group', on the other hand, just echoes the
>>> description in the minibuffer. Neither of the commands actually change
>>> how the *Group* buffer looks. Is that not what you're seeing?
>>
> Which of the above servers hosts the groups that aren't producing
> descriptions correctly? I only use news.gmane.io. If the server is
> freely accessible I can try reproducing the behavior.
>
There are no descriptions from any servers that I have tried (using
gnus-group-describe-all-groups). You could try news.aioe.org, that is
freely available.
I expect if you don't want a list of all groups with their descriptions
then that is when to use the apropos version, which works.
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
next prev parent reply other threads:[~2020-02-16 15:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-15 16:33 Richmond
2020-02-15 19:57 ` Eric Abrahamsen
2020-02-15 21:02 ` Richmond
2020-02-15 21:43 ` Richmond
2020-02-16 3:50 ` Eric Abrahamsen
2020-02-16 15:58 ` Richmond [this message]
2020-02-16 21:14 ` Eric Abrahamsen
2020-02-16 21:49 ` Richmond
2020-02-16 22:50 ` Eric Abrahamsen
2020-02-17 16:51 ` Richmond
2020-02-17 18:16 ` 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='34275.7378633664$1581868764@news.gmane.org' \
--to=dnomhcir@gmx.com \
--cc=eric@ericabrahamsen.net \
--cc=info-gnus-english@gnu.org \
/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).