Re: [PATCH] postgresql.conf.sample comment alignment.

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: [PATCH] postgresql.conf.sample comment alignment.
Дата
Msg-id YuscR8ogXqUd4ijV@paquier.xyz
обсуждение исходный текст
Ответ на Re: [PATCH] postgresql.conf.sample comment alignment.  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Ответы Re: [PATCH] postgresql.conf.sample comment alignment.  (Julien Rouhaud <rjuju123@gmail.com>)
Re: [PATCH] postgresql.conf.sample comment alignment.  (Peter Smith <smithpb2250@gmail.com>)
Список 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

Вложения

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Amit Langote
Дата:
Сообщение: Re: enable/disable broken for statement triggers on partitioned tables
Следующее
От: Justin Pryzby
Дата:
Сообщение: Re: A test for replay of regression tests