https://bugs.kde.org/show_bug.cgi?id=513819
--- Comment #3 from james anderson <[email protected]> --- (In reply to Maik Qualmann from comment #1) > The BQM script works perfectly fine in Windows as well. > > The variables $NPUT and $OUTPUT are not stored as environment variables; we > can do that if you need them. These variables are directly replaced in the > script with the corresponding file paths, using escaped code. > > Please post a script example that is not working. > > Maik Maik thanks for the super rapid response! I've re-read the documentation and now understand the issue. I was misled by the Notes section of this part of the manual which says this: "Under Windows, environment variables can be accessed in the script with % as a prefix and suffix of variable names (for example %INPUT%). The interpreter used to run the script is cmd.exe." So I just thought that everything would just show up in the environmental variables because that would be a consistent approach and a logical way of doing this, and you're using %INPUT% as an example. If you can populate the variable as well, I'm sure you won't end up with people like me making the same mistake, (and clearly other people are doing the same according to my searches. ) Now that I understand you're doing the substitution in the script I can test that. I'm sure it will work! James -- You are receiving this mail because: You are watching all bug changes.
