Error message file path oddity

[hello_hello]

This could be due to running Avisynth in Wine on Linux, although I suspect not.

Create a basic wrapper function with an argument that will result in an error (in red below) and add it to the auto-loading plugins folder.

function xTrim(clip c, int A, int B) { return Trim(C, A, B, z=1) }

Use the function in a script.
xTrim(0, 0)
The file path to the function in the error message uses forward slashes rather than back slashes.

https://i.ibb.co/tw3FpPcj/Screenshot-2025-11-20-21-13-25.gif

[Jamaika]

Xtrim works for me. ;)
function xTrim(clip c, int A, int B) { return Trim(C, A, B, true) }

[wonkey_monkey]

Probably best put in the Avisynth thread, or raise an issue on Github. It happens on Windows too, and looks like it's down to PluginManager.cpp recording .avsi filenames using .generic_string() instead of .string().

[pbristow]

Both are perfectly valid as input under Windows 10 (I just checked this is still true by doing "cd d:/dirname" and "cd d:\dirname" in CMD, PowerShell, and Explorer), but the system always reports the results with backslashes. So for consistency it would be nice to change it, but other than that, is it causing (or likely to cause) any issues?

[Asmodian]

I like using forward slashes, '\' is too often an escape character. It still feels weird as a long time DOS user.

[hello_hello]

Both are perfectly valid as input under Windows 10 (I just checked this is still true by doing "cd d:/dirname" and "cd d:\dirname" in CMD, PowerShell, and Explorer), but the system always reports the results with backslashes. So for consistency it would be nice to change it, but other than that, is it causing (or likely to cause) any issues?

I can't imagine it's causing any problems, but I had no idea forward slashes could be used for file paths in Windows. I definitely had no idea it'd been possible for so long.
https://retrocomputing.stackexchange.com/questions/28344/since-when-does-windows-support-forward-slash-as-path-separator

Out of curiosity I checked, and they don't work for Wine's implementation of Explorer, but they do for cmd.exe (with the result shown using backslashes).

[pbristow]

I like using forward slashes, '\' is too often an escape character. It still feels weird as a long time DOS user.

Word!

Mind you, I grew up on Primos, where the delimiter was "greater than" (">") - which I would read aloud as "leads to". So much more logical. =;o}