Description

You kindly implemented my feature request #2350. Since I haven't yet used periods within code blocks of commit messages very often in the past, I never noticed until now. For example, if you have the following git commit message:

Fix compound interest

 * Fix bug in class `PropertyEditor` that set the wrong value to `SavingsPlan.compoundInterest`
 * Add calculation of non-compound interest to class `SavingsPlan`

an unwanted backslash is put before each period. And iirc, in my work environment, where I program in C++ this also happens for colons like e.g. in C++ namespaces. Perhaps this happens with other special characters, too. See the attached screenshot below.

By the way, I believe the standard VS Code commit message view renders bullet points correctly, if you use an asterisk for enumeration. Perhaps this could be integrated with this fix/change.

Thank you.

GitLens Version

17.0.2

VS Code Version

Version: 1.98.2 (system setup)
Commit: ddc367ed5c8936efe395cffeec279b04ffd7db78
Date: 2025-03-12T13:32:45.399Z
Electron: 34.2.0
ElectronBuildId: 11161602
Chromium: 132.0.6834.196
Node.js: 20.18.2
V8: 13.2.152.36-electron.0
OS: Windows_NT x64 10.0.19045

Git Version

git version 2.34.1.windows.1

Logs, Screenshots, Screen Captures, etc