Coding style suggestions

[ac-stef]

Please

• use git: write useful commit messages
• trust others to use git as well, for example, to use git blame to identify your stuff
• write new code using the same indentation style that is used throughout the existing code
• do not refactor code for "readability" until you actually know the language
• set your editor to not use tabs (there is no agreement on tab width, therefore tabs can not be used at all)
• tag script command changes with DOCREF to make it easier to keep the documentation updated

[Felix-The-Ghost]

set your editor to not use tabs (there is no agreement on tab width, therefore tabs can not be used at all)

Could you expound on this please? (should I offer code in the future)

[flowtron]

Regarding "spaces vs tabs": The net is filled with this discussion, here are three semi-random picks from 10, 5 and 3 years ago:

1. https://softwareengineering.stackexchange.com/questions/57/tabs-versus-spaces-what-is-the-proper-indentation-character-for-everything-in-e
2. https://thenewstack.io/spaces-vs-tabs-a-20-year-debate-and-now-this-what-the-hell-is-wrong-with-go/
3. https://insanelab.com/blog/notes/spaces-vs-tabs/

[Felix-The-Ghost]

Well, I don't see a strong reason to use one over the other. Frankly tabs seems better because it can vary in width to the preference of the viewer and is technically more concise, however if the majority of AC's codebase is already using spaces for indentation, I understand the need for consistency with existing code so I can respect that when submitting work to AC.