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

Re: builtin conversion between tabs and spaces

From
Jonathan del Strother <maillist@steelskies.com>
Date
Oct 15, 2008, 21:02 UTC
Message-ID
<57518fd10810151402p4ea3283anf4b3d175c4e82425@mail.gmail.com>
In-Reply-To
<d4bc1a2a0810151352s6c963e32jc4f492a7c84841dc@mail.gmail.com>

On Wed, Oct 15, 2008 at 9:52 PM, Stefan Karpinski <stefan.karpinski@gmail.com> wrote:

Show 5 quoted lines
> if you consistently use spaces, then tabs_to_spaces will
> always give you back your original version; if you consistently use
> tabs, then spaces_to_tabs will give you back your original version. If
> you use some crazy mix of the two, you cannot reconstruct your
> original without remembering where there were tabs versus spaces,

Just IMO, a crazy mix of tabs and spaces is the only _sane_ thing to do. Using tabs for the initial indentation, plus spaces for alignment of function arguments / comments / whatever, is the only way of getting a layout that will both look right regardless of the tab size, and allow a viewer to alter the indentation size.

Previous: Stefan KarpinskiNext: Stefan Karpinski
Message 5 of 11 in “builtin conversion between tabs and spaces”
  1. Stefan KarpinskiOct 15, 2008
  2. Stefan KarpinskiOct 15, 2008
  3. Alex RiesenOct 15, 2008
  4. Stefan KarpinskiOct 15, 2008
  5. Jonathan del StrotherOct 15, 2008
  6. Stefan KarpinskiOct 15, 2008
  7. Stefan KarpinskiOct 15, 2008
  8. A Large Angry SCMOct 15, 2008
  9. Stefan KarpinskiOct 16, 2008
  10. Johannes SixtOct 15, 2008
  11. Stefan KarpinskiOct 15, 2008

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.