Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Richmond <dnomhcir@gmx.com>
Cc: info-gnus-english@gnu.org
Subject: Re: Gnus Describe Group and Gnus Describe All Groups
Date: Sat, 15 Feb 2020 19:50:14 -0800	[thread overview]
Message-ID: <87eeuvqjgp.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <66fe4c89-0d50-2006-1aea-2a40e966496e@gmx.com> (Richmond's message of "Sat, 15 Feb 2020 21:02:03 +0000")

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?
>
> No, not in the first case gnus-group-describe-all-groups
> I am seeing a list of all the groups, including those
> I am not subscribed to,

FWIW, I think this is sub-optimal behavior, as well -- at the very
least, there should be two different paths for seeing descriptions of
groups you're subscribed to, and all groups on a server.

[...]

> There is one error message in the messages buffer:
>
> Reading descriptions file via nntp...               
> Opening nntp server on news.aioe.org...done         
> Reading descriptions file...done                    
> Reading descriptions file via nnfolder...           
> Couldn't read newsgroups descriptions               

I think this just means there are no group descriptions on an nnfolder
server.

> Opening nntp server on news.gmane.io...             
> Opening nntp server on news.gmane.io...done         
> Reading descriptions file...done                    
> Reading descriptions file via nntp...               
> Opening nntp server on news.mozilla.org...done      
> Reading descriptions file...done                    

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.


Eric
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english

  parent reply	other threads:[~2020-02-16  3:50 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 [this message]
2020-02-16 15:58       ` Richmond
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=87eeuvqjgp.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=dnomhcir@gmx.com \
    --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).