# Minimum code snippet to demonstrate the issue
set -Eeuo pipefail
Flag emphasis is inconsistent for some reason when the -o flag is "glued" to others.

Bug or feature?
(_I don't remember the term for writing the flags like that; feel free to educate/edit me_)
I don't personally know _why,_ but it does look like o is "special"
see: https://www.gnu.org/software/bash/manual/bash.pdf page 48

@deathaxe That's the documentation for test. This ticket is special behavior for set, as generated from
In the Builtin docs, -o/+o looks different from the other options, but it's unclear to me whether this means that it's ineligible for use as a "compacted" option.
setset [--abefhkmnptuvxBCEHPT] [-o option-name] [argument 鈥 set [+abefhkmnptuvxBCEHPT] [+o option-name] [argument 鈥
Side notes:
[--a鈥 or [-a鈥?)The -o is special in not being a switch only, but being followed by an option name. While set -Eeuo pipefail is valid, set -Eeou pipefail wouldn't be. The algorithm to generate the syntax would need to be tweaked to allow short-options at the end of short-options-compact only (if merged).
Maybe match: (?:\s+|^)((\-|\+)(?:[o]|[abefhkmnptuvxBCEHPT]+o?))(?=\s|;|$||))`
About [--a...] : I guess it denotes the -- token in an unlucky way.
See usage output: set: usage: set [-abefhkmnptuvxBCHP] [-o option-name] [--] [arg ...]
About PDFs: DuckDuckGo just pushed me there. The Windows snipping tool just was the easiest way here. Just was to lazy to think about it more carefully ;-)
Most helpful comment
I don't personally know _why,_ but it does look like
ois "special"https://github.com/sublimehq/Packages/blob/759d6eed9b4beed87e602a23303a121c3a6c2fb3/ShellScript/commands-builtin-shell-bash.sublime-syntax#L553