Community
Participate
Working Groups
Build Identifier: Build id: I20110613-1736 Since 3.7.0 there is now a dialog window that allows users to choose which whitespace characters should be displayed. They seem to be divided context-wise into three categories: leading, trailing and in between. This feature, while very cool and useful for PHP developers (since having leading or trailing white space within a source can lead to a host of trouble, such as corrupt binary output or the inability to set headers) is almost perfect, except for one point: The newline characters (\r and \n) can only be checked at trailing. I believe that in the case of newline characters, the leading, trailing and in between should work at a global level (per file) and should mean before first non-whitespace character (leading), after the last non-whitespace character (trailing) and in between for the rest of the lines. This way, PHP developers can easily spot newlines after the ?> tag without having distracting \n markers Reproducible: Always
(In reply to comment #0) > The newline characters (\r and \n) can only be checked at trailing. I believe > that in the case of newline characters, the leading, trailing and in between > should work at a global level (per file) Changing the meaning of leading, trailing, in between for \r and \n would be confusing. And I do not think the gains are significant. If I understand correctly you just want to know if there are any new lines at the end of the file but not otherwise. To do this you can enable line numbers in the editor, if there are empty line numbers at the end of the file you will see the line numbers on the left. Closing this as WONTFIX.
I guess that works too. Thanks for the quick reply
