Closed
Bug 427141
Opened 16 years ago
Closed 16 years ago
nsIProcess should open command consoles when running batch files
Categories
(Core :: XPCOM, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: pomocJava, Unassigned)
References
Details
(Keywords: regression)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; pl; rv:1.8.1.13) Gecko/20080311 Firefox/2.0.0.13 Build Identifier: process.run changed behavior. with my extenstion I would like to open command prompt window or see batch output and now it's impossible? Reproducible: Always Steps to Reproduce: ... path = System32+"cmd.exe" var file = Components.classes["@mozilla.org/file/local;1"] .createInstance(Components.interfaces.nsILocalFile); file.initWithPath(path); var process = Components.classes["@mozilla.org/process/util;1"] .createInstance(Components.interfaces.nsIProcess); process.init(file); var args = ["/k", "cd", varParam]; process.run(false, args, args.length); ... Actual Results: no console window Expected Results: the same as Gecko 1.8 - console window visible
Reporter | ||
Updated•16 years ago
|
Version: unspecified → Trunk
Reporter | ||
Comment 1•16 years ago
|
||
/cvsroot/mozilla/xpcom/threads/nsProcessCommon.cpp Is it possible to expose CREATE_NO_WINDOW flag in nsIProcess interface?!
Comment 2•16 years ago
|
||
This was an intentional change, made in bug 421751. nsIProcess is frozen and can't easily be changed.
Blocks: 421751
Keywords: regression
Comment 3•16 years ago
|
||
Adam, in bug 421751 comment #14 I gave you an example of how to run a command, with arguments, in a visible command window. Why do you still say it's impossible? FWIW, on other platforms we do not (and did not before bug 421751) open any command windows when executing external processes.
Reporter | ||
Updated•16 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•