Why no return value for plugin command run() method?

[stupid]

Please help me understand…

What is the reason behind a plugins run() method not allowing for the returning of values? Say from within one command you wanted to run another command… but you need to know whether something failed before proceeding. This is what return values are for…

psudo code:

result = sublime.active_window().run_command(‘go_do_this’)
if result successful:
yay
else:
ohcrap do this instead

(note: result is always none)

---

I’m guessing there is a good reason for this default behavior and that I lack understanding. But if there really isn’t any reason why this shouldn’t be possible with some custom code, could someone please point me in the right direction to accomplish this task?

Thanks

[math2001]

Indeed, it’s a bit weird, but you can’t…

What command are you actually running? Is it a custom one?

---

Might save time to some people: passing by reference doesn’t seem to work…

---

@stupid (weird name, no?) Have a look here: https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet

[stupid]

Howdy,

don’t know if you saw, but a few guys chimed in on this issue on this thread the other day. Yeah, I’ve got a ton of custom commands and some get pretty involved. So far the only way to do this is courtesy of @rwols -hat tip sir- He figured out a way… its a little dirty… but I’m going with it…

run_command return code

Yes, what I wrote is for an external process like make and such. It wasn't clear to me if that is what you wanted. Anyway, do as @OdatNurd says and consider writing regular Python functions if you want to get return values. I do still wish commands could return values. Imagine that being possible; all of the sublime module could then be ApplicationCommands, no? And if so, you could get JSON return values from the command line, as in $ subl --command packages_path, if it were PackagesPathComm…

as for my handle… lol