| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>, Daniel Gustafsson <daniel(at)yesql(dot)se> |
| Cc: | Melanie Plageman <melanieplageman(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Add trim_trailing_whitespace to editorconfig file |
| Date: | 2024-02-15 15:57:05 |
| Message-ID: | b4d04521-c231-4b1e-a00d-f0088128fbd3@eisentraut.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 15.02.24 10:26, Jelte Fennema-Nio wrote:
> On Wed, 14 Feb 2024 at 23:19, Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
>>> +1 from me. But when do we want it to be false? That is, why not
>>> declare it true for all file types?
>>
>> Regression test .out files commonly have spaces at the end of the line. (Not
>> to mention the ECPG .c files but they probably really shouldn't have.)
>
> Attached is v2, which now makes the rules between gitattributes and
> editorconfig completely identical. As well as improving two minor
> things about .gitattributes before doing that.
Is there a command-line tool to verify the syntax of .editorconfig and
check compliance of existing files?
I'm worried that expanding .editorconfig with detailed per-file rules
will lead to a lot of mistakes and blind editing, if we don't have
verification tooling.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2024-02-15 16:14:35 | Re: MAINTAIN privilege -- what do we need to un-revert it? |
| Previous Message | Peter Eisentraut | 2024-02-15 15:49:45 | Re: Replace current implementations in crypt() and gen_salt() to OpenSSL |