You misunderstood both the author and my sentence example "Often" refers to the fact that most of his ops are word/sentence/... , and these have no ambiguity,

You misunderstood both the author and my sentence example "Often" refers to the fact that most of his ops are word/sentence/... , and these have no ambiguity, thus you don't need visual feedback. But he's wrong about the lack of ambiguity, his most common text objects are not clear. That's the fundamental error Then the issue in the sentence example isn't that you can't define it or apply the definition, it's that you can't easily visually parse it due to various sentence-ending symbols not being sentence-ending, so it becomes ambiguous and requires extra effort > And some of those edge cases can easily be mitigated. Sure, and another easy mitigation is to switch to a more ergonomic editing model where you get it by default > Syntax highlighting should already provide a visual indicator in this case. If there's a mismatch, that's likely a bug. Of course there is, vim motions aren't scope based while syntax highlighting is. Unless you have a mod to make them scope based, which... introduces Uncertainty!