🐛 Syntax highlighting doesn't work when the second file path includes a backslash on Windows

[Mixaz017]

When passing a path containing backslashes \ as the second argument (PLUS_FILE), the output have no syntax highlighting.
File contents:

Expected output (without backslashes):

Actual output (with backslashes):

git -v: git version 2.38.1.windows.1 (problem still occurs with --no-gitconfig)
delta -V: delta 0.14.0
less -V: less 608 (Spencer V8 regular expressions)

It feels quite odd because this problem doesn't occur when the first file path (MINUS_FILE) contain backslashes, and delta is still reading file contents correctly.
A workaround is to replace backslashes with forward slashes, but it would be nice to be able to use backslashes since that is the "native" path on Windows, and PowerShell auto completion inserts backslashes so users have to manually fix the path.

[dandavison]

Thanks @Mixaz017, that certainly looks like a bug.

[th1000s]

Should be fixed with #1222 - the git output placed " around the filename because of the backslash, so the extension got parsed as ts" instead of ts.

[Mixaz017]

Thank you @th1000s , I can confirm that the PR fixes the issue.

[Mixaz017]

The issue is gone in 0.15.0! Closing.