We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi Stephen @stephenharris ,
I wasn't able to run the msgmerge from within the pot. Running it manually from the shell worked fine, but not from Grunt.
pot
The patch below worked (with Node 0.12).
I am not sure, but it looked to me like async spawn wasn't working well under Windows, even with CygWin.
Check if you want to replace all execs with execSyncs. All works fast enough, so why do you need async?
exec
execSync
Thank you!
if (poFilePaths && options.msgmerge) { var execSync = require('child_process').execSync; poFilePaths.forEach(function (poFile) { execSync('msgmerge -vU ' + poFile + ' ' + potFile); }); }
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi Stephen @stephenharris ,
I wasn't able to run the msgmerge from within the
pot
. Running it manually from the shell worked fine, but not from Grunt.The patch below worked (with Node 0.12).
I am not sure, but it looked to me like async spawn wasn't working well under Windows, even with CygWin.
Check if you want to replace all
exec
s withexecSync
s. All works fast enough, so why do you need async?Thank you!
The text was updated successfully, but these errors were encountered: