Horton

Re: Add trim_trailing_whitespace to editorconfig file

Jelte Fennema-Nio <postgres@jeltef.nl>

View thread View on postgr.es
From: Jelte Fennema-Nio <postgres@jeltef.nl>
To: Peter Eisentraut <peter@eisentraut.org>
Cc: Andrew Dunstan <andrew@dunslane.net>, Daniel Gustafsson <daniel@yesql.se>, Melanie Plageman <melanieplageman@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Matthias van de Meent <boekewurm+postgres@gmail.com>
Date: 2024-08-09T14:09:59Z
Lists: pgsql-hackers 
On Fri, 9 Aug 2024 at 15:16, Peter Eisentraut <peter@eisentraut.org> wrote:
> -*.sgml         whitespace=space-before-tab,trailing-space,tab-in-indent
> -*.x[ms]l       whitespace=space-before-tab,trailing-space,tab-in-indent
> +*.py           whitespace=space-before-tab,trailing-space,tab-in-indent,tabwidth=4
> +*.sgml         whitespace=space-before-tab,trailing-space,tab-in-indent,tabwidth=1
> +*.xml          whitespace=space-before-tab,trailing-space,tab-in-indent,tabwidth=1
> +*.xsl          whitespace=space-before-tab,trailing-space,tab-in-indent,tabwidth=2
>
> Why add tabwidth settings to files that are not supposed to contain tabs?

That's there so that the generated .editorconfig file the correct
indent_size. I guess another approach would be to change the
generate_editorconfig.py script to include hardcoded values for these
4 filetypes.

Commits

  1. Add script to keep .editorconfig in sync with .gitattributes

  2. Remove non-existing file from .gitattributes