Good news: I've added this and it will be in the next Studio release.
Settings > Editor now has a Keyword casing option with three choices:
- Canonical (the default) keeps the current behaviour, so
Var, If, For Each and friends are corrected to their standard spelling.
- Lowercase writes them as
var, if, for each, end if and so on.
- Preserve as typed leaves whatever casing you type alone.
The rest of the formatter still runs in every mode, so you keep the automatic spacing, operator formatting and member-name corrections; only the keyword spelling changes. The setting also applies to autocomplete suggestions and to the closers inserted by Shift+Return, so with Lowercase you will not see an end if get "corrected" back to End If the moment the caret leaves the line. It works the same in project code and in IDE Scripts, it is saved with your other Studio preferences, and it takes effect on the next line you format or complete rather than rewriting anything you already have open.
A couple of deliberate boundaries: built-in type names such as Integer and String keep their standard spelling in every mode, as they are type names rather than control keywords, and member names such as AudioPlayer.Loop are never touched by the keyword setting. Objo is case-insensitive, so none of this changes how a program runs.
The Feedback entry is here: https://feedback.objo.dev/feature/1735