berkus / enso

Automatically exported from code.google.com/p/enso
Other
1 stars 0 forks source link

Help command fails on Windows #5

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
When I use the Help command on Windows, Enso crashes with the following
stack trace:

   File "C:\Documents and Settings\Jono\My
Documents\enso-open-source\win32\enso_
win32\input\InputManager.py", line 69, in run
    def run(*args): return _InputManager.InputManager_run(*args)
  File "C:\Documents and Settings\Jono\My
Documents\enso-open-source\core\enso\e
vents.py", line 283, in onKeypress
    func( eventType, keyCode )
  File "C:\Documents and Settings\Jono\My
Documents\enso-open-source\core\enso\q
uasimode\__init__.py", line 197, in onKeyEvent
    self.__quasimodeEnd()
  File "C:\Documents and Settings\Jono\My
Documents\enso-open-source\core\enso\q
uasimode\__init__.py", line 337, in __quasimodeEnd
    self.__executeCommand( activeCommand, cmdName )
  File "C:\Documents and Settings\Jono\My
Documents\enso-open-source\core\enso\q
uasimode\__init__.py", line 360, in __executeCommand
    cmd.run()
  File "C:\Documents and Settings\Jono\My
Documents\enso-open-source\core\enso\c
ontrib\help.py", line 122, in run
    self.__htmlHelp.view()
  File "C:\Documents and Settings\Jono\My
Documents\enso-open-source\core\enso\c
ontrib\help.py", line 97, in view
    webbrowser.open( fileUrl )
  File "C:\Python24\lib\webbrowser.py", line 43, in open
    get().open(url, new, autoraise)
  File "C:\Python24\lib\webbrowser.py", line 250, in open
    os.startfile(url)
WindowsError: [Errno 3] The system cannot find the path specified:
'file://///C|
/docume%7E1/jono/locals%7E1/temp/ensoHelpowrsjz.html'
INFO    [Fri Mar 21 12:24:43 2008 src\InputManager\AsyncEventThread.cxx
L249]: a
sync event thread: quit signal received.
INFO    [Fri Mar 21 12:24:43 2008 src\InputManager\AsyncEventThread.cxx
L303]: C
losed invisible window.

Original issue reported on code.google.com by ebj...@gmail.com on 21 Mar 2008 at 5:28

GoogleCodeExporter commented 9 years ago

Original comment by ebj...@gmail.com on 21 Mar 2008 at 5:36

GoogleCodeExporter commented 9 years ago
This shouldn't be hard to fix, I'll take care of it.

Original comment by var...@gmail.com on 24 Mar 2008 at 4:02