On Tue, Sep 30, 2014 at 2:27 PM, Stephan Beal <[email protected]> wrote:
> On Tue, Sep 30, 2014 at 6:26 PM, Ron W <[email protected]> wrote: > >> On the command line, I typically pipe command (including fossil) output >> to less, which has its own settings for filtering tabs. >> > > Which highlights the major problem with tabs: they were (25+ years ago) > useful for saving a bit of space, but every program is free to interpret > them differently, and thus their utility suffers. In ~20 years in the I.T. > field i have _never_ worked on a project (professional nor open source) > which preferred hard tabs over spaces, and projects which have debated the > topic have always ended up choosing spaces over tabs, primarily because > they are 100% predictable, whereas tabs are 100% unpredictable. i am aware > of a small handful of projects which prefer/require them, but... i think > they're crazy for doing so ;). > Every place I've worked has at least strongly discouraged tabs. And since the rise of indentation sensitive "languages" (eg, YAML, Python and others), tabs are officially banned. I do know of an open source project that requires only tabs for indentation. The stated rational being to allow contributors to set their editors' tab to whatever indentation increment desired. The project also discourages use of code formatting tools "to avoid introducing extraneous differences".
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
