From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: 61325@debbugs.gnu.org
Subject: bug#61325: 30.0.50; Jokes in GNUS manual
Date: Tue, 07 Feb 2023 23:10:37 +0800 [thread overview]
Message-ID: <87a61p7bpu.fsf@yahoo.com> (raw)
In-Reply-To: <87wn4tedtx.fsf@localhost> (Ihor Radchenko's message of "Tue, 07 Feb 2023 14:43:06 +0000")
Ihor Radchenko <yantar92@posteo.net> writes:
> Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text
> editors" <bug-gnu-emacs@gnu.org> writes:
>
>>>> 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!
>>>
>>> Thanks.
>>> I also partially understand the joke.
>>> My main problem is the last sentence, which I am not sure if it is
>>> technical or still part of the joke.
>>>
>>> You can even group the Emacs sex groups as a sub-topic to either the
>>> Emacs groups or the sex groups—or both!
>>>
>>> The paragraph structure is basically:
>>>
>>> <technical description><joke><half joke, half technical description>
>>>
>>> Such structure is difficult to understand, especially if the joke itself
>>> is not understood.
>> ...
>>> Not when the jokes stay on the way of understanding the technical parts.
>>
>> They do not. End of discussion.
>
> I kindly disagree. 3.16 Group Topics section was difficult to
> understand _for me_ precisely because of the jokes. I will elaborate
> below.
>
>> Where I come from, it is generally said that a person who deliberately
>> tries to find problems with something is trying to ``pick pricks''.
>> They are usually able to find some problems, because the problems they
>> report tend to, by definition, rely on their own testimony: ``I don't
>> understand'', ``I'm offended by'', etc.
>>
>> Such people generally ruin the day for everyone else wherever they
>> appear.
>
> Upon hearing about the problem and checking the specifically indicated
> sections in the manual, I tend to agree with the person being offended.
> Not because I am not offended (I am not), but because, as I stated
> earlier, I believe that jokes should not complicate the understanding.
>
>> Whoever reported the problem with the Gnus manual, which has not seen
>> other such reports in over 20 years, certainly sounds like one such
>> individual. And if you don't understand the manual, then it is not a
>> problem with the jokes therein. Just read it again until you do.
>> How many people can understand the following sentence without reading it
>> at least once or twice?
>
> Absence of bug reports does not imply that the manual is easy to
> understand. I do not say that it is incomprehensible, but the examples I
> pointed to do make it harder to understand. Won't it be an improvement
> to make the manual easier to understand for more people?
>
>> XcmsCIELabClipL
>>
>> This brings the encountered out-of-gamut color specification into the
>> screen's color gamut by reducing or increasing CIE metric lightness
>> (L*) in the CIE Lab color space until the color is within the
>> gamut. If the Psychometric Chroma of the color specification is beyond
>> maximum for the Psychometric Hue Angle, then while maintaining the
>> same Psychometric Hue Angle, the color will be clipped to the CIE Lab
>> coordinates of maximum Psychometric Chroma. See
>> `XcmsCIELabQueryMaxC'. No client data is necessary.
>>
>> Is color management, thus, an evil which should be persecuted by hordes
>> of crusaders?
>
> I do not see any problem with the provided paragraph. Yes, it contains a
> lot of unfamiliar terms, but they appear to be necessary to describe the
> technical information. In contrast, jokes do not convey any new
> information. They are good to have as an _occasional_ distraction - a
> break that may be necessary to simplify understanding; but not good when
> they make understanding more difficult.
>
> Imagine a joke inserted into your example, on top of all other
> unfamiliar terms:
>
>> This brings the encountered out-of-gamut (not gonad, mind you) color
>> specification into the screen's color gamut by reducing or
>> increasing (let's not think further) CIE metric lightness (L*) in the
>> CIE Lab color space until the color is within (mmm...) the gamut.
>
> Would you find it helpful or at least neutral to have these extra jokes
> when trying to understand the above sentence?
I didn't see ``let's not think further'' in the Gnus manual. And no,
your additions do not make it harder for me to understand that sentence.
next prev parent reply other threads:[~2023-02-07 15:10 UTC|newest]
Thread overview: 136+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 16:01 bug#61325: 30.0.50; Jokes in GNUS manual Ihor Radchenko
2023-02-06 16:20 ` dick
2023-02-12 6:11 ` Jean Louis
2023-02-06 16:27 ` Eli Zaretskii
2023-02-06 16:38 ` Ihor Radchenko
2023-02-06 16:42 ` Ihor Radchenko
2023-02-06 16:51 ` Eli Zaretskii
2023-02-06 17:04 ` Ihor Radchenko
2023-02-18 13:59 ` Petteri Hintsanen
2023-02-19 10:43 ` Ihor Radchenko
2023-02-20 5:18 ` Richard Stallman
2023-02-06 17:23 ` Pankaj Jangid
2023-02-06 17:49 ` Ihor Radchenko
2023-02-06 18:37 ` Pankaj Jangid
2023-02-06 18:45 ` Ihor Radchenko
2023-02-07 2:04 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-07 11:24 ` Ihor Radchenko
2023-02-07 12:36 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-07 13:01 ` Ihor Radchenko
2023-02-07 14:03 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-07 14:43 ` Ihor Radchenko
2023-02-07 15:10 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-02-07 16:15 ` Ihor Radchenko
2023-02-08 1:28 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-08 11:40 ` Ihor Radchenko
2023-02-08 11:41 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-08 11:59 ` Ihor Radchenko
2023-02-08 12:50 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-15 14:55 ` Ihor Radchenko
2023-02-16 1:29 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-17 12:25 ` Ihor Radchenko
2023-02-18 4:19 ` Richard Stallman
2023-02-18 11:14 ` Ihor Radchenko
2023-02-20 5:19 ` Richard Stallman
2023-02-22 13:43 ` Eli Zaretskii
2023-02-25 4:09 ` Richard Stallman
2023-02-08 12:36 ` Eli Zaretskii
2023-02-12 6:38 ` Jean Louis
2023-02-09 4:28 ` Richard Stallman
2023-02-07 19:45 ` Pankaj Jangid
2023-02-07 19:56 ` Ihor Radchenko
2023-02-09 4:28 ` Richard Stallman
2023-02-07 14:15 ` dick
2023-02-07 15:09 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-07 15:17 ` Eli Zaretskii
2023-02-08 8:11 ` Michael Albinus
2023-02-08 12:31 ` Eli Zaretskii
2023-02-08 12:59 ` Michael Albinus
2023-02-07 15:41 ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-09 4:28 ` Richard Stallman
2023-02-09 16:44 ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-12 4:03 ` Richard Stallman
2023-02-08 4:31 ` Richard Stallman
2023-02-08 4:46 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-12 6:46 ` Jean Louis
2023-02-15 14:47 ` Ihor Radchenko
2023-02-16 1:27 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-17 12:38 ` Ihor Radchenko
2023-02-17 5:22 ` Jean Louis
2023-02-19 4:50 ` Richard Stallman
2023-02-19 5:04 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-22 4:33 ` Richard Stallman
2023-02-22 6:02 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-26 2:59 ` Richard Stallman
2023-02-08 13:06 ` dick
2023-02-08 15:35 ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-08 16:06 ` dick
2023-02-15 14:37 ` Ihor Radchenko
2023-02-16 1:34 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-17 12:49 ` Ihor Radchenko
2023-02-19 4:50 ` Richard Stallman
2023-02-19 10:36 ` Ihor Radchenko
2023-02-19 11:01 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-19 11:13 ` Eli Zaretskii
2023-02-20 11:50 ` Ihor Radchenko
2023-02-20 12:34 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-07 13:29 ` Ihor Radchenko
2023-03-07 20:02 ` No Wayman
2023-03-07 20:12 ` Eli Zaretskii
2023-02-19 12:24 ` Stefan Kangas
2023-02-19 13:05 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-19 13:45 ` Stefan Kangas
2023-02-20 18:29 ` Gregory Heytings
2023-02-21 2:30 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-22 4:34 ` Richard Stallman
2023-02-22 4:35 ` Richard Stallman
2023-03-07 13:48 ` Ihor Radchenko
2023-03-08 0:22 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-08 14:05 ` Ihor Radchenko
2023-03-09 1:14 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-10 4:25 ` Richard Stallman
2023-03-10 7:03 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-09 4:28 ` Richard Stallman
2023-03-08 5:34 ` Jean Louis
2023-03-08 14:13 ` Ihor Radchenko
2023-03-09 1:21 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-13 14:50 ` Jean Louis
2023-03-09 4:26 ` Richard Stallman
2023-03-10 11:33 ` Ihor Radchenko
2023-03-10 11:34 ` Ihor Radchenko
2023-03-10 12:06 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-10 12:37 ` Eli Zaretskii
2023-03-10 12:41 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-13 15:01 ` Jean Louis
2023-02-19 15:56 ` Drew Adams
2023-02-20 12:00 ` Ihor Radchenko
2023-02-20 12:37 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-20 14:28 ` Michael Albinus
2023-02-20 14:34 ` Ihor Radchenko
2023-02-20 17:01 ` Drew Adams
2023-02-20 11:55 ` Ihor Radchenko
2023-02-27 3:26 ` Richard Stallman
2023-02-19 5:07 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-18 4:19 ` Richard Stallman
2023-02-19 10:25 ` Ihor Radchenko
2023-02-15 15:34 ` Stefan Kangas
2023-02-15 16:00 ` Robert Pluim
2023-02-18 4:19 ` Richard Stallman
2023-02-17 5:24 ` Jean Louis
2023-02-19 4:50 ` Richard Stallman
2023-02-08 13:42 ` Visuwesh
2023-02-12 6:56 ` Jean Louis
2023-02-12 6:32 ` Jean Louis
2023-02-14 4:51 ` Richard Stallman
2023-02-14 11:17 ` Jean Louis
2023-03-09 4:05 ` Sam James
2023-03-09 14:10 ` Dmitry Gutov
2023-03-09 14:17 ` Robert Pluim
2023-03-09 16:57 ` Dmitry Gutov
2023-03-09 17:06 ` Robert Pluim
2023-03-09 20:10 ` Jose A. Ortega Ruiz
2023-03-10 10:53 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-13 15:05 ` Jean Louis
2023-09-06 6:53 ` Stefan Kangas
2023-09-06 7:10 ` Ihor Radchenko
2023-09-06 7:30 ` Stefan Kangas
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a61p7bpu.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=61325@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=yantar92@posteo.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).