Interesting, but feels ever so slightly wrong. Mixing tabs and spaces is the source of all the hatred us tab-users get and it makes for the most unreadable files whenever someone's indentation widths don't agree with the source code's.
With tabs only, you are free to display them as whatever width your eyes enjoy seeing the code wave along; with spaces, your code looks uniform everywhere across the globe. With mixed tabs and spaces, the moment someone tries to look with a fully 4 units wide indent length (that is, tab-size), all your indentations start to look messy (0, 4, 4, 8, 8, 12, 12...).
I'm personally quite happy that this broken method isn't supported by Sublime text, only portable ones are. Sorry to hear that such a great and large project like FreeBSD decided to use such a mess.
Interesting, but feels ever so slightly wrong. Mixing tabs and spaces is the source of all the hatred us tab-users get and it makes for the most unreadable files whenever someone's indentation widths don't agree with the source code's.
With tabs only, you are free to display them as whatever width your eyes enjoy seeing the code wave along; with spaces, your code looks uniform everywhere across the globe. With mixed tabs and spaces, the moment someone tries to look with a fully 4 units wide indent length (that is, tab-size), all your indentations start to look messy (0, 4, 4, 8, 8, 12, 12...).
I'm personally quite happy that this broken method isn't supported by Sublime text, only portable ones are. Sorry to hear that such a great and large project like FreeBSD decided to use such a mess.