On 11/24/2012 08:05 PM, Volker Braun wrote:
You talk about trailing whitespace as if getting rid of it were a worthy goal in itself. It is not. Humans don't care about trailing whitespace, we don't see it unless you misconfigure your editor. Its purely for the
Maybe you don't care, but I surely do care about trailing whitespace, just like I care about having my lines between 75-80 columns long to improve readability.
It has happened often that I start editing some lines in sage and I suddenly find myself having to delete a lot of trailing whitespace characters on the line I am appending to or editing something. I see the line ending at 10 columns, where the visible portion ends, but I try to go to the end of the line and see I am far away at column 120. It is only a minor annoyance, but it would be nice to not encourage people to introduce such whitespaces in the first place. It helps me, personally, to keep to my limit of 75-80 columns and makes editing files a little less painful. Of course, you can choose to not agree with my personal preferences. :)
benefit of automated merge tools. If we disallow patch hunks that change trailing whitespace only then the needs of merge tools are satisfied and there is no further need for any policy beyond that.
I don't understand why merge tools should care about trailing whitespaces. They should only care about the lines that have been edited. I don't think any of the merge tools run anything similar to "diff --ignore-space-change".
-- You received this message because you are subscribed to the Google Groups "sage-devel" group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en.