From: Jonathan Corbet <corbet@lwn.net>
To: Bru Moreira-Guedes <codeagain@codeagain.dev>,
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: Tue, 07 Mar 2023 10:13:44 -0700 [thread overview]
Message-ID: <87356gpjqv.fsf@meer.lwn.net> (raw)
In-Reply-To: <20230228222035.k227xb3okt2lbksn@guidai>
Bru Moreira-Guedes <codeagain@codeagain.dev> writes:
> The old text about tabs failed to clearly convey the message that the
> TAB character is used for indentation. It also gives the misleading
> impression that it's trying to "redefine" what a tab (the 0x09 ASCII
> character) is when it says "tabs are 8 characters".
>
> 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).
>
> The present patch clarifies the tabs text on such aspects.
>
> Signed-off-by: Bru Moreira-Guedes <codeagain@codeagain.dev>
> ---
> Documentation/process/coding-style.rst | 14 ++++++++------
> 1 file changed, 8 insertions(+), 6 deletions(-)
>
> diff --git a/Documentation/process/coding-style.rst b/Documentation/process/coding-style.rst
> index 007e49ef6cec..9a0205fa7ed3 100644
> --- a/Documentation/process/coding-style.rst
> +++ b/Documentation/process/coding-style.rst
> @@ -18,23 +18,25 @@ Anyway, here goes:
> 1) Indentation
> --------------
>
> -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.
I guess I really don't see how this kind of tweaking helps things; this
text has stood for a couple of decades or so without evident
misunderstandings.
...and I'm totally mystified as to why we've redefined pi from 3 to 5?
> 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
Adding typos doesn't really help either.
Thanks,
jon
next prev parent reply other threads:[~2023-03-07 17:18 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
2023-03-07 17:13 ` Jonathan Corbet [this message]
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=87356gpjqv.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=codeagain@codeagain.dev \
--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).