Errors when running DashDoc command

[farcaller]

Errors when running DashDoc command

[farcaller]

That's quite surprising, do you have the openbinary at /usr/bin/open?

[farcaller]

Also, can you please run this in ST3 python console (opened via **ctrl+**): import os; os.environ['PATH']`?

[MrCrunchwrap]

Output of which open is /usr/bin/open

Output of import os; os.environ['PATH'] is '/usr/local/share/npm/bin:/usr/local/bin:/opt/local/bin'

[MrCrunchwrap]

Not too familiar with Python, but it doesn't look like this PATH is the same as my Unix PATH environment variable. Do I need to add something to this Python environment?

[farcaller]

Well, while this is a bug I can fix on DashDoc side, did you consider fixing your environment? Other strange things might happen if you don't have at least /bin and /usr/bin in your PATH.

[MrCrunchwrap]

Understandably so. I'm not entirely sure how it got changed, as DashDoc was working yesterday. Some kind of magic is happening because now I launched ST3 and output of os.environ['PATH'] is '/usr/bin:/bin:/usr/sbin:/sbin'

Problem is solved now. Thanks for the input!

[Teggy]

@farcaller: Do you consider to replace 'open' by '/usr/bin/open' in the subprocess.call(...)? Sounds reaonsable/safe to do so — the location of open is unlikely to change.

[farcaller]

Done.