bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#61325: 30.0.50; Jokes in GNUS manual


From: Po Lu
Subject: bug#61325: 30.0.50; Jokes in GNUS manual
Date: Tue, 07 Feb 2023 20:36:34 +0800
User-agent: Gnus/5.13 (Gnus v5.13)

Ihor Radchenko <yantar92@posteo.net> writes:

> Po Lu <luangruo@yahoo.com> writes:
>
>>> 3.15 Exiting Gnus has
>>>
>>> ...
>>> 3.16 Group Topics
>>> ...
>>
>> I think this joke is fairly obvious for anyone who has tried to browse a
>> public news server.
>
> May you please elaborate which joke you are referring to?

This one:

3.16 Group Topics

    If you read lots and lots of groups, it might be convenient to group
    them hierarchically according to topics.  You put your Emacs groups over
    here, your sex groups over there, and the rest (what, two groups or so?)
    you put in some misc section that you never bother with anyway.  You can
    even group the Emacs sex groups as a sub-topic to either the Emacs
    groups or the sex groups—or both!  Go wild!

I do understand the rest as well.

> Agree. My other points remain. In particular, about joking on sex topic,
> which is present in the same paragraph.

There are such newsgroups on the Usenet, so why would cracking jokes
about them be any different from cracking jokes about any other
newsgroup?

Seriously, anyone who finds that joke offensive needs to grow up and get
a life!

> I do not mind not understanding. But I do prefer to have manuals written
> in such a way that I can at least distinguish jokes from the technical
> information I actually need to use GNUS. I admit that the paragraph
> about "kill files" is clearly distinguishable as a joke. Not so much for
> 3.16 Group Topics where jokes and non-jokes are rather mixed.
>
> Also, note that Gnus is also email client. Are people who intend to use
> GNUS for email supposed to understand Newsgroup terminology in order to
> use GNUS?

No, but they are not expected to understand the jokes in the manual for
a _newsreader_ either.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]