Backtick in log path

[user1016]

In macOS, does the shell attempt to interpret backticks in logfile paths?

Given a profile named "Hawai`i", clicking on the yellow warning triangle in the "Log" column gives this popup:

Cannot open file "/Users/me/Library/Application Support/FreeFileSync/Logs/Hawai`i 2025-05-30 141619.413 [Warning].html".

Exit code 2: /bin/sh: -c: line 0: unexpected EOF while looking for matching ``'
/bin/sh: -c: line 1: syntax error: unexpected end of file [open "%x"]

The logfile does exist and can be opened by navigating to it in the Finder and double-clicking.

[therube]

Backtick does hold special meaning in Linux.

https://unix.stackexchange.com/questions/48392/understanding-backtick

Removing the backtick in the dirname should fix things, I'd think.
I imagine if you were to create a .html file, test`me.html & try to "execute" that, you might see something similar.

And it is sh that is throwing the error, so I wouldn't think that an attempt to sanitize things on the FFS would be of any help.

[Zenju]

Fixed for the next release.

[user1016]

Confirmed -- thank you so much!