Stephan Beal wrote: > --===============1471853227== > Content-Type: multipart/alternative; boundary=089e0139fcda1d63f205044c8930 > > --089e0139fcda1d63f205044c8930 > Content-Type: text/plain; charset=UTF-8 > > 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 ;).
Matches my experience too. By all means configure your editor to indent to whatever degree you (or the project) prefers, but have it use spaces, not hard tabs, to do so. -- Will _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
