[Exception… “Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [koIInvocation.getExecutable]” nsresult: “0x80004005 (NS_ERROR_FAILURE)” location: “JS frame :: chrome://runinline/content/sdk/runinline.js :: this._runFile :: line 80” data: no]
Thinking something had gone amiss in Chrome (I have no line 80 in the html file), I edited preferences to use Firefox but the error message didn’t change. Perhaps I didn’t change the right preference. Can someone please tell me where I have run amiss. I am running Komodo IDE 10 on Linux (Mint).
Thanks for any help.
Edit: If I use the dropdown and select open in Komodo tab it works OK but opens a new tab. If I select Firefox or Chrome, it works OK in the browser. Just not in Komodo. Color me confused.
It looks like you are trying to use the “run-inline” feature, which just executes code and shows the result in a popup dialog. What exactly are you trying to do?
You don’t understand the meaning of Run Inline. This is intended to be used whenever you want to execute some code (PHP, NodeJS, Ruby, Python, etc.). For example, If you will press this button in a ruby file, this command will be executed:
$ ruby /tmp/runinline.rb # (actually, STDIN will be read by that)
This is not intended to be used as browser preview.
This is a bug. You can’t use
run inline on an html file. There shouldn’t be a Dynamic button showing. That is the root of the problem here. @louyo correctly assumed that that button should do something for the current file but it doesn’t and it fails.
I’ll file a bug report. Thanks for bringing this up, @louyo .
6 posts were split to a new topic: Run Inline using SpiderMonkey or V8
A post was merged into an existing topic: Run Inline using SpiderMonkey or V8
- Run Inline doesn’t work properly if you don’t select
<?php in a php file. (which is not the case in most situations).
The actual issue has been resolved. Me and Carey described how Run Inline works and why it’s not working for OP.
Everything is now in their own topics. We will continue to discuss in them.
Thanks for cleaning up @Defman