To my previous post: that would break visual code alignment if tabs are used
for such alignment inside lines of code, not at beginning; tabs should be
replaced there by variable number of spaces. Yet someone can use literal tabs
inside strings (though mostly escape sequences are used), so the
But it works already with `#? replace(sub="\t",by=" ")`.
Allowing tabs means "allowing mixed" because TABs are what the are. They are
not "4 spaces in the package of one `\t`" they are meant as stops at fixed
positions starting from 0 and if you use a Tabstop of 4 and you use indentation
of 2 you will have 1 tab and two spaces in front of your text
For existing libraries you can transform the input on load and transform it
back on save. Not particularly elegant, but gives you lots of freedom and also
solves other issues (like stripping trailing whitespace).
Yes, for your example you are right. I have never done such type of alignment
myself in my code, but indeed there seems to exist people who like that. Indeed
for that type of alignment proportional fonts do not work. Really a nice
example.
> Indent width can always be freely rendered
Yes,
> The big problem I've had with tabs was in team programming,
But there is no problem, as long as tabs and spaces are not mixed for
indentation purpose in a single file. And no one wants to allow mixing.
There is one big advantage of tabs: Indent width can be freely configured,
without the
> But forbidding tabs I don't like.
You stated you use gedit, which handles indentation (via the tab key) with
either spaces or tabs, and that is very simple to configure.
Most decent editors have this feature. For me I prefer Nim not allowing tabs. I
don't see the point of having tabs used
> With proportional fonts unfortunately 2 spaces generate a tiny indent step.
> So I have to use 3 or 4 spaces, or finally a tab! I think I will do the later
> with the replace command mentioned above. The only disadvantage is that
> github puts 8 spaces for each tab, so I have to convert files
