timrray Posts: 24 26/09/2024	timrray Posts: 24 Hello! I just wanted to report a problem I'm having with the latest version. All of my "windows command" entries stopped working recently. When I run them, I get "The system cannot find the path specified". Upon looking at the command line being launched, it looks like there are double quotes around the actual command I am trying to run. For example, for the windows command "ipconfig /flushdns", Symenu winds up running "cmd.exe /k" ""ipconfig /flushdns"" (note the double quotes around the actual windows command I specified in the Symenu entry).
	link
Gianluca Administrator Posts: 1313 26/09/2024	Gianluca Administrator Posts: 1313 Hello timrray, Wow... I think this is the first time I receive a bug report so detailed. Thank you for this. You are right, with the last version I changed the escaping command system. Before that version escaping a forbidden char was done with the ^ char. So for example: C:\(MeAndYou) that's a perfectly allowed name in Windows but created some problems if executed in a process, was changed in: C:\^(MeAndYou^) But this method had some drawbacks for example with the & character. The solution with the double quotes seems a good one with a minimum impact and instead... some commands fail because of this one. So a command like: "ipconfig" works well regardless the double quotes but: "ipconfig /all" won't work at all.... Windows mysteries... So what can we do now? I think I could try to recognize when the command contains a path and only in that case I can escape it. This solution should fix any problem. What do you think about it? BTW how are you able to sniff the command send to the shell? I'm asking because it could be a useful technique for me too.
	+1 link

---