When I type the path to an executable in this dialog, or select an executable with the browse button, it appears that NPP does not surround it with double quotes. So if the path contains any spaces, the app will not run. The same is true with the Save button -- no double quotes.
If I edit shortcuts.xml (with another editor, so my changes don't get clobbered) and add the quotes around the path, then the app will run when I restart NPP and select the item from the Run menu.
Aaron.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Actually, Windows+R adds the double quotes if you browse to the item (rather than just typing a path), but NPP F5 does not. Would be a nice enhancement!
Thanks,
Aaron.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Post this on IdeaTorent, it may make for better Windows integration by having the same behaviour, which is not too much nonsensical - I'd be wary of following Windows' quirks too closely.
CChris
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
When I type the path to an executable in this dialog, or select an executable with the browse button, it appears that NPP does not surround it with double quotes. So if the path contains any spaces, the app will not run. The same is true with the Save button -- no double quotes.
If I edit shortcuts.xml (with another editor, so my changes don't get clobbered) and add the quotes around the path, then the app will run when I restart NPP and select the item from the Run menu.
Aaron.
Actually, Windows+R adds the double quotes if you browse to the item (rather than just typing a path), but NPP F5 does not. Would be a nice enhancement!
Thanks,
Aaron.
You can add the double quotes in the F5 broser. This is the expected behaviour I believe - like in the Windows+R Run command from Windows.
CChris
Post this on IdeaTorent, it may make for better Windows integration by having the same behaviour, which is not too much nonsensical - I'd be wary of following Windows' quirks too closely.
CChris