git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Igor Djordjevic <igor.d.djordjevic@gmail.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] help: colorize man pages
Date: Sun, 23 May 2021 13:25:59 +0200	[thread overview]
Message-ID: <6642528a-b270-5862-bfdc-7bfa22682c2f@gmail.com> (raw)
In-Reply-To: <60a97c12d96a_85723208d4@natae.notmuch>


On 22/05/2021 23:48, Felipe Contreras wrote:
> 
> Language is understood bit by bit. To properly understand the sentences
> that follow you first need to understand the sentences that preceed.

Except you can't deliberately chop and butcher mentioned sentences in 
order to "understand" them in isolation, as the meaning is largely 
determined by context - and yes, the following sentences as well.

You focus on seeing the trees, but you're missing the forest.

> I know what you said in the rest of the message, which is precisely why
> it does not follow, and since you ignored my argument, let me state it
> with logic symbols for the record.
> 
>   It is reasonable to configure certain software such as a text editor
>   to use color or other ANSI attributes sparingly (such as the reverse
>   attribute for a status bar)
> 
> We extract part of the message:
> 
>   It is reasonable to configure a text editor to use color sparingly
> 
> The first sentence implies the second, no information is changed.
> 
> ---
> 
> You interpret that as:
> 
>   It is reasonable to allow the user to configure a text editor to use
>   color sparingly
> 
> This is obviously a different sentence. You introduced a part that was
> not there.
> 
> Now we use logic symbols to transform your sentence:
> 
>   p = the user configures a text editor to use color sparingly
>   q = it is reasonable to allow the user
> 
> This is what you said: if p -> q. The contraposition is: ~q -> ~p.
> 
> Therefore you said:
> 
>   It is not reasonable to allow the user to configure a text editor to
>   not use color sparingly.
> 
> This is a fact.
> 
> What you said doesn't make sense.
> 
> ---
> 
> This what no-color.org said:
> 
>   It is reasonable to configure a text editor to use color sparingly
> 
> By doing the same contraposition as above we get that it's the same as:
> 
>   It is not reasonale to configure a text editor to not use color
>   sparingly.
> 
> Or in other words.
> 
>   It is not reasonable to configure a text editor to use colors heavily.
> 
> If it's the developers doing that, then that statement is correct.
> 
> This is my interpretation. My interpretation holds to scrutiny; yours
> does not.
> 
> They meant the developers. They are not trying to tell users what to do.
> 
> Cheers.

You are overthinking the whole thing (or the piece(s) you focused on, in 
fact missing the thing as a whole completely), making it unnecessarily 
complicated for yourself.

The NO_COLOR[1] homepage text, read in its entirety and even if not 
perfect, seems clear enough for everyone who wants to understand it. 
I'm sorry if it's not clear for you, I'm afraid I can't help any 
further.

And while I find your armchair analysis amusing, you'll pardon me for 
not taking any more part in it as, unfortunately, I don't have that 
much time at my hands to waste.

Cheers, Buga
--
[1]: https://no-color.org/

  reply	other threads:[~2021-05-23 11:26 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-18  1:01 Felipe Contreras
2021-05-18  1:19 ` brian m. carlson
2021-05-18  3:22   ` Felipe Contreras
2021-05-18 23:49     ` brian m. carlson
2021-05-19  1:08       ` Junio C Hamano
2021-05-19  2:07         ` brian m. carlson
2021-05-19  6:09           ` Junio C Hamano
2021-05-19  8:41             ` Ævar Arnfjörð Bjarmason
2021-05-19 10:36               ` Felipe Contreras
2021-05-21  0:58               ` brian m. carlson
2021-05-21 18:09                 ` Felipe Contreras
2021-05-21 19:48                   ` Igor Djordjevic
2021-05-21 21:20                     ` Felipe Contreras
2021-05-21 22:10                       ` Igor Djordjevic
2021-05-21 23:04                         ` Felipe Contreras
2021-05-22 18:38                           ` Igor Djordjevic
2021-05-22 21:48                             ` Felipe Contreras
2021-05-23 11:25                               ` Igor Djordjevic [this message]
2021-05-23 14:48                                 ` Felipe Contreras
2021-05-21 22:47                     ` Igor Djordjevic
2021-05-21 23:32                     ` Junio C Hamano
2021-05-19  9:26       ` Ævar Arnfjörð Bjarmason
2021-05-19 10:10         ` Jeff King
2021-05-19 11:45           ` Felipe Contreras
2021-05-19 11:19         ` Felipe Contreras
2021-05-19 12:21           ` Felipe Contreras
2021-05-20  1:55         ` brian m. carlson
2021-05-20  2:23           ` Junio C Hamano
2021-05-20  3:05             ` Felipe Contreras
2021-05-20  3:28               ` Junio C Hamano
2021-05-20  3:48                 ` Felipe Contreras
2021-05-20  2:45           ` Felipe Contreras
2021-05-19 10:25       ` Felipe Contreras

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=6642528a-b270-5862-bfdc-7bfa22682c2f@gmail.com \
    --to=igor.d.djordjevic@gmail.com \
    --cc=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --subject='Re: [PATCH] help: colorize man pages' \
    /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

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).