So... we could use tabs for indenting code..
But what if the IDE just recognized if a file is indented with 2, 3, 4 or 8 spaces, and then treats any such number of spaces as a tab when displaying the code? Wouldn't that be way easier?
So... we could use tabs for indenting code..
But what if the IDE just recognized if a file is indented with 2, 3, 4 or 8 spaces, and then treats any such number of spaces as a tab when displaying the code? Wouldn't that be way easier?
Wow, that was quite a battle.
#tabsvsspaces
This is what I imagine people's code looks like when they complain about the forced indentation in #python.
And yes, this code is correct.
#programming #c #formatting #indentation #tabsvsspaces #whitespace #developers #developerexperience #debugging #fail #goodluck
Reading about how tabs for indentation are an accessibility issue for some suddenly makes me feel like I should switch to tabs in all my projects.
Are there any accessibility concerns that would actually point to using spaces instead of tabs? Or is it just familiarity? Assuming you work with a code style where you don't need to align things to columns that don't divide nicely to tab levels.
It's impossible for a computer nerd to hear "TABs" without thinking about the age-old conflict about tabs vs spaces for indentation of program text.
In the disability context #TabsVsSpaces could be about how people without disabilities go and design bad spaces that work only for them.
Just to confuse things. π
New Kate instance, new setup. Tabs, not spaces!