| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
| Cc: | Daniel Gustafsson <daniel(at)yesql(dot)se>, 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-04-04 15:23:28 |
| Message-ID: | 0ada3dd0-4d71-4e81-8424-ecb8c23c6905@eisentraut.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 04.04.24 16:58, Jelte Fennema-Nio wrote:
> On Thu, 4 Apr 2024 at 15:25, Peter Eisentraut<peter(at)eisentraut(dot)org> wrote:
>> Everybody has git. Everybody who edits .gitattributes can use git to
>> check what they did.
> What CLI command do you use to fix/ gitattributes on all existing
> files? Afaict there's no command to actually remove the trailing
> whitespace that git add complains about. If you don't have such a
> command, then afaict updating gitattributes is also essentially
> blind-updating.
I don't have a command to fix files automatically, but I have a command
to check them:
git diff-tree --check $(git hash-object -t tree /dev/null) HEAD
That's what I was hoping for for editorconfig-check, but as I said, the
experience wasn't good.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jelte Fennema-Nio | 2024-04-04 15:28:25 | Re: Add trim_trailing_whitespace to editorconfig file |
| Previous Message | Melanie Plageman | 2024-04-04 15:20:35 | Re: Streaming read-ready sequential scan code |