{"thread":{"id":"18697","subject":"Whitespace options","startedAt":"2009-04-02T19:18:19Z","lastAt":"2009-04-03T02:39:33Z","messageCount":3,"participants":["Gerd Knops","Joshua Juran","Miles Bader"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"110238","messageId":"3C72F4A7-9B7A-44D0-B13D-FD534EB02C27@bitart.com","threadId":"18697","inReplyTo":null,"subject":"Whitespace options","fromName":"Gerd Knops","fromEmail":"gerti-git@bitart.com","sentAt":"2009-04-02T19:18:19Z","receivedAt":"2009-04-02T19:18:19Z","isPatch":false,"sender":{"key":"gerti-git@bitart.com","avatar":null},"body":"Hi all,\n\nI think there should be a whitespace option that ignores lines that  \nconsists completely of whitespace vs lines with actual trailing  \nwhitespace preceded by non-whitespace.\n\nThe reason is that many editors (especially those supporting indent- \nbased code folding) keep 'empty' lines at the current indentation  \nlevel. git (with default settings) flags all those lines.\n\nI know I could just remove 'trailing-space' from 'core.whitespace',  \nbut I would actually still like be notified about the case where a  \nline that is not whitespace only ends with trailing whitespace.\n\nThanks\n\nGerd\n"},{"id":"110260","messageId":"612E4BF7-3230-462A-8A82-1E268F9A7632@gmail.com","threadId":"18697","inReplyTo":"3C72F4A7-9B7A-44D0-B13D-FD534EB02C27@bitart.com","subject":"Re: Whitespace options","fromName":"Joshua Juran","fromEmail":"jjuran@gmail.com","sentAt":"2009-04-03T02:15:54Z","receivedAt":"2009-04-03T02:15:54Z","isPatch":false,"sender":{"key":"jjuran@gmail.com","avatar":null},"body":"On Apr 2, 2009, at 12:18 PM, Gerd Knops wrote:\n\n> I think there should be a whitespace option that ignores lines that  \n> consists completely of whitespace vs lines with actual trailing  \n> whitespace preceded by non-whitespace.\n\n+1\n\n> The reason is that many editors (especially those supporting indent- \n> based code folding) keep 'empty' lines at the current indentation  \n> level.\n\nAs do some users, out of personal preference.\n\nJosh\n"},{"id":"110262","messageId":"buoab6yjw9m.fsf@dhlpc061.dev.necel.com","threadId":"18697","inReplyTo":"3C72F4A7-9B7A-44D0-B13D-FD534EB02C27@bitart.com","subject":"Re: Whitespace options","fromName":"Miles Bader","fromEmail":"miles@gnu.org","sentAt":"2009-04-03T02:39:33Z","receivedAt":"2009-04-03T02:39:33Z","isPatch":false,"sender":{"key":"miles@gnu.org","avatar":"https://gravatar.com/avatar/01069b69593af7bff28e2f97afeb3644ae6fe2f5f56cb3a8cf34c5fb8c36efe5?d=mp&s=160"},"body":"Gerd Knops <gerti-git@bitart.com> writes:\n> The reason is that many editors (especially those supporting indent-\n> based code folding) keep 'empty' lines at the current indentation\n> level. git (with default settings) flags all those lines.\n\nThat sounds like very fragile behavior on the part of the editor -- it\nsounds like they assume that all source code was created by their\neditor, and will never be touched by any other tool...\n\n-Miles\n\n-- \nSuburbia: where they tear out the trees and then name streets after them.\n"}]}