git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Fw: Tabs vs Spaces - Handle like CLRF?

From
JHJames Hughes <james@pyrosoftsolutions.co.uk>
Date
May 19, 2021, 15:55 UTC
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
Next: Jeff King
Message 1 of 2 in “Fw: Tabs vs Spaces - Handle like CLRF?”
  1. James HughesMay 19, 2021
  2. Jeff KingMay 19, 2021

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.