>> > Another approach would be to add a mode that colors trailing >> > whitespace in that ugly greeny/yellowy color that DrRacket uses for >> > the "your code is more than 102 columns" warning. >> >> +1 to this. I think I’d definitely like this independent of a mechanism to >> trim on save. > > +1
Also +1. This is like Emacs' `show-trailing-whitespace', which I enable for most prog modes. Things like trailing whitespace, or files not ending with a newline, cause Git noise. It's nice to clean them up. However I've found it problematic to change them automagically (and especially on save), as opposed to me doing it deliberately and with review. For example from using `show-trailing-whitespace' I can report there's a lot of it in Racket sources. But it might be nicer to have commits dedicated to removing it (maybe even for whole repos at once), as opposed to the cleanups being sprinkled among many commits intended to accomplish other things? Just a thought. -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
