From: James Hughes <james@pyrosoftsolutions.co.uk>
Date: Wed, 19 May 2021 15:55:46 GMT
Subject: Fw: Tabs vs Spaces - Handle like CLRF?
Message-ID: <GJHGZLcAwaihWwWmzAt8bdOKWi8JiupQxVUXCs1FwKTOmn2yvWEjI8DDTmDaBA48lzz4pGQ-JmwmHKSrEU2NCpdyxXW-ExqZcgxKEmL-454=@pyrosoftsolutions.co.uk>
In-Reply-To: <2AzjQ7QDayLsqCbYQzwoZhJvvWKVAlBXStsOtYN03i41hVJcbYou0Je8Sxqec8UB0j0ZAfhKosA_IymlTez2X1J-voxUfG65EA-Zm0YWU10=@pyrosoftsolutions.co.uk>

Hi all,

We have the ability to automagically handle CLRF issues when we commit and check-out to handle different dev environments.

A lot of us will also hold religious beliefs as to which is the correct way to indent, tabs or spaces.

Since it's simple a whitespacing issue, is there any reason we couldn't handle this in a similar way to CLRF? Give devs the choice to commit with tabs/spaces as per their organisations requirements and then convert to their preference on checkout?

All the best,

James