You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Dragging a file from the explorer into the terminal enters its path. Since the path could contain special characters, it is escaped with double quotes " on Windows or single quotes ' on Ubuntu 24. The problem is that trogon escapes the input an additional time. So the executed command looks something like this:
script.py --output '"D:\path\to\file.txt"'
The parsed path therefore still contains the quotes leading to a FileNotFoundError.
I'd suggest, that trogon should detect when the input is already escaped and not escape it an additional time.
The text was updated successfully, but these errors were encountered:
Thanks for the report @IceFreez3r—this does not appear to be the case in macOS, so seems Windows and Linux specific. I unfortunately don't have access to either type of system at the moment so not sure if I'll be able to effectively test this myself, but happy to accept PRs to this effect!
Dragging a file from the explorer into the terminal enters its path. Since the path could contain special characters, it is escaped with double quotes
"
on Windows or single quotes'
on Ubuntu 24. The problem is that trogon escapes the input an additional time. So the executed command looks something like this:script.py --output '"D:\path\to\file.txt"'
The parsed path therefore still contains the quotes leading to a
FileNotFoundError
.I'd suggest, that trogon should detect when the input is already escaped and not escape it an additional time.
The text was updated successfully, but these errors were encountered: