From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Bru Moreira-Guedes <codeagain@codeagain.dev>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Patch Watchbox <patch-reply@codeagain.dev>
Subject: Re: [PATCH] coding-style.rst: indentation: Clarify tabs text
Date: Wed, 1 Mar 2023 09:28:32 +0700 [thread overview]
Message-ID: <45757233-6152-9971-d987-e0ce27f92fe2@gmail.com> (raw)
In-Reply-To: <20230228222035.k227xb3okt2lbksn@guidai>
On 3/1/23 05:20, Bru Moreira-Guedes wrote:
> It might be misleading, especially for some autistic readers for whom
> English is not the first language and whose tendency to interpret things
> more literally might be present (i.e., my very own self).
>
I'm also actually autistic (∞) :) ...
> The present patch clarifies the tabs text on such aspects.
>
Clarify tabs description?
> -Tabs are 8 characters, and thus indentations are also 8 characters.
> -There are heretic movements that try to make indentations 4 (or even 2!)
> -characters deep, and that is akin to trying to define the value of PI to
> -be 3.
> +The Linux Kernel uses the TAB character for indentation, as in the K&R
> +style. Tabs are meant to be viewed as 8-characters, and thus
> +indentations are meant to be seen as 8 characters as well. There are
> +heretic movements that try to use spaces for indentation, or make tabs
> +viewed as 4 (or even 2!) characters, and that is akin to trying to
> +define the value of PI to be 5.
>
"In the context of kernel code, tabs are intended to be 8-characters
indentation."
> Rationale: The whole idea behind indentation is to clearly define where
> a block of control starts and ends. Especially when you've been looking
> at your screen for 20 straight hours, you'll find it a lot easier to see
> how the indentation works if you have large indentations.
>
> -Now, some people will claim that having 8-character indentations makes
> +Now, some people will claim that viewint 8-character tab indentations makes
viewing
>
> -In short, 8-char indents make things easier to read, and have the added
> +In short, 8-char tab size make things easier to read, and have the added
8-char tab indents (for consistency with above)?
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2023-03-01 2:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 22:20 [PATCH] coding-style.rst: indentation: Clarify tabs text Bru Moreira-Guedes
2023-03-01 2:28 ` Bagas Sanjaya [this message]
2023-03-07 17:13 ` Jonathan Corbet
2023-03-12 21:57 ` Bru Moreira-Guedes
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=45757233-6152-9971-d987-e0ce27f92fe2@gmail.com \
--to=bagasdotme@gmail.com \
--cc=codeagain@codeagain.dev \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patch-reply@codeagain.dev \
/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).