Prefs → Advanced, consistent styling
Some Observations
In Preferences → Advanced, there’s some inconsistency in the styles for the listed items:
Badge
Font to use for the badge.
Maximum height of the badge
Maximum width of the badge
Right Margin
Should the badge render in bold type?
Top MarginDebugging
Log stats about text drawing performance to the console.
[…]
The very first item ends with a full stop, then the following items don’t, until we get to “Should the badge render in bold type”, then we go back to a simple title. Both “Right Margin” and “Top Margin” use title capitalization.
The next section on debugging ends each item with a full stop. After that there’s a few items that are missing full stops.
WWAD?
The Apple HIG article, Use the Right Capitalization Style in Labels and Text suggests this:
Element | Capitalization Style | Examples |
---|---|---|
Labels that are not full sentences (for example, group box or list headings) | Title | Mouse Speed Total Connection Time Account Type |
Options that are not strictly labels (for example, radio button or checkbox text), even if they are not full sentences |
Sentence | Checking for new software… Are you sure you want to quit? |
Some Proposals
-
Length: List items should be succinct.
Style like a subject line. Perhaps aim for a maximum title length, some of the items are especially long. - Capitalization: Use sentence capitalization throughout.
-
Question marks: There are only three items presented as a question when many more could be.
These items should be reworded and have the question marks removed. - Message: If further detail is needed, that goes on the “message” line which should end with a full stop.
This item could be looked at in particular:
When you press an arrow key or other function key that transmits the modifiers, should Option be translated to Meta?
If this is set to No then it will be translated to Alt.
The “subject” line is longer than the “message” line, most of that detail should go into the supplementary “message” line. As a very basic suggestion:
Translate Option key to Meta key
When you press an arrow key or other function key that transmits the modifiers, should Option be translated to Meta? If this is set to No then it will be translated to Alt.
The “subject” line describes the “what”, the “message” line tells us “why”.
If you’re okay with this I can create a PR with fixes for these and a few other things and then the specifics can be worked out.
And thank you, George, for all your hard work on iTerm2!