Vinicius Jose Latorre <address@hidden> writes:
Well, indeed the old whitespace-buffer had reported
where the bogus whitespace had happened.
Instead of reporting, the new whitespace-mode
displays visually the bogus whitespace.
Is it ok if the new whitespace-buffer is removed?
Maybe a better alternative should be to create a
whitespace-report command which reports like the old
whitespace-buffer.
My personal opinion is that the old whitespace mode was pretty wacky,
E.g., how about:
+ `suspicious-whitespace-mode' -- highlights only "suspicious"
whitespace, i.e., that which probably should be removed. This is
sort of like the old "whitespace-buffer" command, but implemented as
a proper mode, or like your "whitespace-mode", but only highlights
suspicious whitespace. [dunno about the term "suspicious", but you
know what I mean]
+ `cleanup-whitespace' -- removes suspicious whitespace [same
definition as suspicious-whitespace-mode]
-Miles