On Thu, Oct 18, 2007 at 01:02:32AM +0300, Jari Aalto wrote: > * Wed 2007-10-17 Michael Witten <mfwitten@xxxxxxx> > * Message-Id: E29971BA-7306-4570-8383-26D0C9C0B814@xxxxxxx > > On 17 Oct 2007, at 3:17:08 AM, Luke Lu wrote: > > > >> But I still haven't seen any compelling arguments against the "all > >> space" case > > > > Overhead! > > > > If you use 8 spaces instead of one tab, > > that's using up 7x more space! > > Software is the right place to worry about optimization. We should trust > SCM to make proper and efficient deltas. If not, algorithms need > improvemnts. > > Any cross platform development or electronic exchange is guaranteed to > be interpreted correctly when policy enforces "only spaces" > > As we have already seen in numerous times in this thread, using tabs > will - eventually - be interpreted in some editor, in some display, in > some encironment using some tools ... incorrectly or different than the > author intended. Simply because editors are configurable and we cannot > know what settings they may have when they load the file in. > > There is no such problem with spaces. There is such problem with spaces. A lot of editors will just insert tabs to indent a new line when the previous you were typing begins with enough spaces, in which case you end up with spaces and tabs mixed all the way. It ends up being worse than all tabs. Mike - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
