I'm somewhere between "don't mind" and "avoid". Using tabs in my free software causes me to get a steady trickle of confused mail from people who have loaded it into an editor which interprets a physical tab differently from the standard (notably Visual Studio, which AIUI can be configured into sensible mode but not per-project), and also I sometimes find it actually inconvenient during editing because tabs make complicated editor macros less predictable. So I quite like no-tabs as a policy. But I haven't adopted it yet, mostly because detabbing all my existing source would be a tedious and annoying job with plenty of scope for messing things up and would also have unhelpful effects on things like "svn blame".
Work enforces a no-tabs policy by automatic detabbing at checkin time (and you have to specially mark each makefile as exempt from this when you create it). This is surprisingly infrequently a problem, and generally seems to work well for everybody. (Though I don't think I'd go that far myself, although I might be tempted by refusing a checkin that contained an unsanctioned tab.)
IWBNI annotate commands had an option to skip whitespace-only changes. Maybe some do. It'd also be useful for the case where you change the indentation on some bit code because it's become conditional or repeated or something.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
(no subject)
Date: 2007-04-03 12:47 pm (UTC)Work enforces a no-tabs policy by automatic detabbing at checkin time (and you have to specially mark each makefile as exempt from this when you create it). This is surprisingly infrequently a problem, and generally seems to work well for everybody. (Though I don't think I'd go that far myself, although I might be tempted by refusing a checkin that contained an unsanctioned tab.)
(no subject)
Date: 2007-04-03 05:19 pm (UTC)