With various Atom syntax themes, I have a hard time reading split-diff when "Show Word Diff" is enabled (especially when the underlying code uses various colors because of syntax highlighting). Thus, I usually want this setting to be disabled. I can do so in the split-diff configuration menu or by setting the split-diff config boolean diffWords to false.
However, even if I disable this behavior, one use of git-time-machine always brings it back.
After a minute of grepping, it looks git-time-machine might modify this setting here.
I understand why you might need to override the default rightEditorColor and leftEditorColor, and for UX reasons, I even understand overriding scrollSyncType. But is it really necessary to override diffWords and for that matter ignoreWhitespace?
I would prefer that git-time-machine not modify the user's global diffWords and ignoreWhitespace settings.
With various Atom syntax themes, I have a hard time reading split-diff when "Show Word Diff" is enabled (especially when the underlying code uses various colors because of syntax highlighting). Thus, I usually want this setting to be disabled. I can do so in the split-diff configuration menu or by setting the split-diff config boolean
diffWords
to false.However, even if I disable this behavior, one use of git-time-machine always brings it back.
After a minute of grepping, it looks git-time-machine might modify this setting here.
I understand why you might need to override the default
rightEditorColor
andleftEditorColor
, and for UX reasons, I even understand overridingscrollSyncType
. But is it really necessary to overridediffWords
and for that matterignoreWhitespace
?I would prefer that git-time-machine not modify the user's global
diffWords
andignoreWhitespace
settings.