| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Smith <smithpb2250(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: [PATCH] postgresql.conf.sample comment alignment. |
| Date: | 2022-08-04 01:09:27 |
| Message-ID: | YuscR8ogXqUd4ijV@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2022-08-04 01:13:00 | Re: A test for replay of regression tests |
| Previous Message | Amit Langote | 2022-08-04 00:46:28 | Re: enable/disable broken for statement triggers on partitioned tables |