Re: [PATCH] postgresql.conf.sample comment alignment. - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: [PATCH] postgresql.conf.sample comment alignment.
Date
Msg-id YuscR8ogXqUd4ijV@paquier.xyz
Whole thread Raw
In response to Re: [PATCH] postgresql.conf.sample comment alignment.  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Responses Re: [PATCH] postgresql.conf.sample comment alignment.
Re: [PATCH] postgresql.conf.sample comment alignment.
List pgsql-hackers
On Wed, Aug 03, 2022 at 12:58:04PM +0200, Alvaro Herrera wrote:
> On 2022-Aug-01, Tom Lane wrote:
>> One idea for avoiding confusion is to legislate that we won't
>> use tabs at all in this file (which we could enforce via
>> .gitattributes, I think).
>
> +1.

That's not the first time this 4- or 8-character tab issue is popping
up around here, so enforcing spaces and having a rule sounds like a
good idea at the end.

>> But that might just be making things equally inconvenient for
>> everybody.
>
> In this situation, the only disadvantaged users are those using a
> non-fixed-width font in their editor, but those are lost souls already.

Haha.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: enable/disable broken for statement triggers on partitioned tables
Next
From: Justin Pryzby
Date:
Subject: Re: A test for replay of regression tests