SCM - commit message box uses the wrong cursor (can be hard to see)

[jacekkopecky]

The SCM/git commit message editor uses a subset of cursor settings, which, in my case, makes it hard to see.

Does this issue occur when all extensions are disabled?: Yes

• VS Code Version: 1.98.0 and latest build from main
• OS Version: Mac and Windows both, not OS-specific

Steps to Reproduce:

1. override cursor style (e.g. block, or width 4) in settings
2. override cursor color in settings.json workbench.colorCustomizations (e.g. "#0d0f")
3. check that the cursor is the correct style and color in text editor
4. check that other fields (e.g. search) do not use the overridden cursor but platform default
5. check that SCM/git commit message edit field uses a thin line cursor in your color rather than your overridden style/width or the platform default

The reason for this bug is that the git commit message uses a monaco editor and not a textarea, so it's affected by the color setting from your theme override but it does not import cursor style or width from the settings.

The gif below shows my green block non-blinking cursor in text editor, default blinking black line cursor in the search field, and a thin green non-blinking cursor in the git commit message. My eyesight is bad, and the commit window cursor is hard to see for me.

[lszomoru]

Verification steps:

• Modify the editor.cursorStyle, and editor.cursorWidth settings
• Confirm that the cursor style/width in the editor matches the cursor style/width in the commit input box

[meganrogge]

@lszomoru neither seem to work for me

Screen.Recording.2025-03-25.at.12.54.25.PM.mov

[jacekkopecky]

@meganrogge thanks for catching that - @lszomoru it's not reacting to settings changes. It needs this around line 1500 in src/vs/workbench/contrib/scm/browser/scmViewPane.ts

		const onDidChangeConfiguration = Event.filter(
			this.configurationService.onDidChangeConfiguration,
			e => {
				return e.affectsConfiguration('editor.accessibilitySupport') ||
					e.affectsConfiguration('editor.cursorBlinking') ||
+					e.affectsConfiguration('editor.cursorStyle') ||
+					e.affectsConfiguration('editor.cursorWidth') ||
					e.affectsConfiguration('editor.emptySelectionClipboard') ||
					e.affectsConfiguration('editor.fontFamily') ||
					e.affectsConfiguration('editor.rulers') ||
					e.affectsConfiguration('editor.wordWrap') ||
					e.affectsConfiguration('scm.inputFontFamily') ||
					e.affectsConfiguration('scm.inputFontSize');
			},
			this._disposables
		);

Sorry that I missed that.

[lszomoru]

@jacekkopecky, no worries. I have pushed a fix which should be in tomorrow's VS Code Insiders release.

[vs-code-engineering]

Issue marked as unreleased but unable to locate closing commit in issue timeline. You can manually reference a commit by commenting \closedWith someCommitSha, or directly add the insiders-released label if you know this has already been released