Closed
Bug 614199
Opened 15 years ago
Closed 14 years ago
cfx does not launch from within "Documents and settings"
Categories
(Add-on SDK Graveyard :: General, defect, P2)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: daniel, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.2.12) Gecko/20101026 Firefox/3.6.12 ( .NET CLR 3.5.30729)
Build Identifier: 0.9
Jetpack does not seem to put path within double quotes causing paths with spaces to break.
Reproducible: Always
Steps to Reproduce:
* Windows XP, SP3
* Python 2.7
Extraciting jetpack to a folder as:
C:\Documents and Settings\user.name\My documents\Projects\Jetpack-Test\jetpack-sdk-0.9>
And then running "cfx docs" gives this:
(C:\Documents and Settings\user.name\My documents\Projects\Jetpack-Test\jetpack-sdk-0.9) C:\Documents and Settings\user.name\My documents\Projects\Jetpack-Test\jetpack-sdk-0.9\bin>cfx docs
python: can't open file 'C:\Documents': [Errno 2] No such file or directory
Actual Results:
Error message given as:
python: can't open file 'C:\Documents': [Errno 2] No such file or directory
Expected Results:
If I move/copy the jetpack folder to c:\jetpack-sdk-0.9 it works as expected:
(C:\jetpack-sdk-0.9) C:\jetpack-sdk-0.9>cfx docs
One moment.
Opening web browser to http://127.0.0.1:8888.
What I assume is that jetpack tries to open
C:\Documents and settings
instead of
"C:\Documents and settings"
Where the first yields a path of just C:\Documents (which does not exist) and to arguments ('and' and 'settings').
Comment 1•15 years ago
|
||
Hmm, indeed!
Note that we're planning to start recommending that folks use the Add-on SDK with the MozillaBuild terminal, since it provides a better environment for using the SDK in a variety of respects, including this one (it doesn't have this problem).
To use the MozillaBuild terminal, download MozillaBuild from <http://ftp.mozilla.org/pub/mozilla.org/mozilla/libraries/win32/MozillaBuildSetup-Latest.exe> and then run its start-l10n.bat file to open the terminal.
Keep in mind that you'll be in a Unix-like environment where changing to the SDK directory is the following command:
cd /c/Documents\ and\ Settings/user.name/My\ documents/Projects/Jetpack-Test/jetpack-sdk-0.9
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 2•15 years ago
|
||
Erm, also, if you use MozillaBuild, you'll need to activate the SDK using the following command (from within the top-level SDK directory) instead of the Windows version of it:
source bin/activate
(Basically, you then use the SDK as if you are on a *nix system rather than Windows.)
Updated•15 years ago
|
Component: Jetpack SDK → General
Product: Mozilla Labs → Add-on SDK
QA Contact: jetpack-sdk → general
Updated•14 years ago
|
Priority: -- → P2
Target Milestone: --- → 1.0
Updated•14 years ago
|
Priority: P2 → --
Target Milestone: 1.0 → ---
Updated•14 years ago
|
Priority: -- → P2
Target Milestone: --- → 1.0
Comment 3•14 years ago
|
||
(automatic reprioritization of 1.0 bugs)
Priority: P2 → P1
Target Milestone: 1.0 → 1.1
Updated•14 years ago
|
Assignee: nobody → myk
Updated•14 years ago
|
Priority: P1 → P2
Target Milestone: 1.1 → 1.3
Updated•14 years ago
|
Summary: cfx does not lauch from within "Documents and settings" → cfx does not launch from within "Documents and settings"
(Pushing all open bugs to the --- milestone for the new triage system)
Target Milestone: 1.3 → ---
Comment 5•14 years ago
|
||
Unassigning myself from bugs I am not actively working on.
Assignee: myk → nobody
I'm not able to reproduce this on my WinXP virtual machine with SDK 1.4.3.
C:\Documents and Settings\XPMUser\addon-sdk-1.4.3>bin\activate.bat
Welcome to the Add-on SDK. Run 'cfx docs' for assistance.
(C:\Documents and Settings\XPMUser\addon-sdk-1.4.3) C:\Documents and Settings\XP
MUser\addon-sdk-1.4.3>cfx docs
Generating documentation...
(C:\Documents and Settings\XPMUser\addon-sdk-1.4.3) C:\Documents and Settings\XP
MUser\addon-sdk-1.4.3>
Not sure if it was fixed IN 1.4 (haven't tried any of the prior versions in my VM), but it no longer seems to be happening for me.
Please reopen if you're still having this problem.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•