From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HTML_MESSAGE,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 19783 invoked from network); 5 Mar 2021 01:49:45 -0000 Received: from minnie.tuhs.org (45.79.103.53) by inbox.vuxu.org with ESMTPUTF8; 5 Mar 2021 01:49:45 -0000 Received: by minnie.tuhs.org (Postfix, from userid 112) id E203A9CA7D; Fri, 5 Mar 2021 11:49:42 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id 5ED659CA68; Fri, 5 Mar 2021 11:49:27 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=pass (1024-bit key; unprotected) header.d=alanlee.org header.i=@alanlee.org header.b="V0ndOdkX"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id 8BCA49CA68; Fri, 5 Mar 2021 11:49:25 +1000 (AEST) X-Greylist: delayed 459 seconds by postgrey-1.36 at minnie.tuhs.org; Fri, 05 Mar 2021 11:49:24 AEST Received: from taz.retrotronics.org (taz.retrotronics.org [66.228.61.155]) by minnie.tuhs.org (Postfix) with ESMTPS id CB8779CA67 for ; Fri, 5 Mar 2021 11:49:24 +1000 (AEST) Received: from www.retrotronics.org (localhost [IPv6:::1]) by taz.retrotronics.org (Postfix) with ESMTP id 1879814D8E0; Thu, 4 Mar 2021 20:41:45 -0500 (EST) DKIM-Filter: OpenDKIM Filter v2.11.0 taz.retrotronics.org 1879814D8E0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alanlee.org; s=default; t=1614908505; bh=lzrzH4sE8wqJb20MN6/sildB2YQ2EOmGpWnG+g6RwQQ=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=V0ndOdkXdcqDnVNh733WhvzUnEXvlOl8wAEKMyyt2Fu4210QyP6Hu6gt/zZLeqqKL YQCGuyOrcwA4+ZKGpEjydGYPydM7QReBir+pUMgXcoqDbK607Z6LrKmk6ch2nDSIBj +kXp0UINdvS6W5azb2opty1bolOQYW2HVvY1mWD4= MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_8b3d880a3c10b1c5ee0442e88b695b86" Date: Thu, 04 Mar 2021 20:41:45 -0500 From: alan@alanlee.org To: Will Senn In-Reply-To: References: Message-ID: X-Sender: alan@alanlee.org User-Agent: Roundcube Webmail/1.3.2 Subject: Re: [TUHS] tabs vs spaces - entab, detab X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: TUHS main list Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" --=_8b3d880a3c10b1c5ee0442e88b695b86 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Easy. Tabs for scope, spaces for everything else - with the later kept to a minimum. That eliminates the spaces per tab part of the discussion. For example if a printf is nested in scope, all lines of the same scope should have the same number of tabs per line. The continuation of text for printf arguments on a second line should have the same number of leading tabs as the printf - then spaces to align the second line where you want it. There should never be any tabs past the initial run at the start of the line. No exceptions! Anyone using spaces to align anything else in the code should be drug in front of a firing line and shot. Anyone using ****** ###### /////// or any other runs of characters in code should be drug in front of a firing line and shot. My $.02 -A On 2021-03-04 11:52, Will Senn wrote: > OK. So, I've been trying to decide (for the last time, I swear) whether to use tabs or spaces in my code... I did a quick pulse-check on the state of argument and it appears to be alive and well in 2021. My question for y'all is, was there a preference in the very early days or not? I saw an article talking about the 20 year feud, but that's not my recollection. In 1994, nobody agreed on this, but I'm sure it predates my entree into the field. I'm thinking the history of entab and detab are somehow related, but I've been wrong on these sorts of thoughts before. What say you? > > Will --=_8b3d880a3c10b1c5ee0442e88b695b86 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=UTF-8

Easy.  Tabs for scope, spaces for everything else - with the later = kept to a minimum.  That eliminates the spaces per tab part of the dis= cussion.

For example if a printf is nested in scope, all lines of the same scope = should have the same number of tabs per line.  The continuation of tex= t for printf arguments on a second line should have the same number of lead= ing tabs as the printf - then spaces to align the second line where you wan= t it.

There should never be any tabs past the initial run at the start of the = line. No exceptions!

Anyone using spaces to align anything else in the code should be drug in= front of a firing line and shot.  Anyone using ****** ###### /////// = or any other runs of characters in code should be drug in front of a firing= line and shot.

My $.02

-A

On 2021-03-04 11:52, Will Senn wrote:

OK. S= o, I've been trying to decide (for the last time, I swear) whether to use t= abs or spaces in my code... I did a quick pulse-check on the state of argum= ent and it appears to be alive and well in 2021. My question for y'all is, = was there a preference in the very early days or not? I saw an article talk= ing about the 20 year feud, but that's not my recollection. In 1994, nobody= agreed on this, but I'm sure it predates my entree into the field. I'm thi= nking the history of entab and detab are somehow related, but I've been wro= ng on these sorts of thoughts before. What say you?

Will
=


--=_8b3d880a3c10b1c5ee0442e88b695b86--