Closed mrmurphy closed 11 years ago
Are you sure this is still a valid problem even with the latest updates in the repository? 3 months ago this commit (https://github.com/justinfx/MayaSublime/commit/434f93db79755cf85824ffb92e884f67a07fb06e) addressed propagating stack traces to the maya script editor.
Example:
# from Sublime
raise TypeError("error") # highlight and send to maya
# from Mayas output
# Traceback (most recent call last):
# File "<string>", line 5, in <module>
# File "<string>", line 1, in <module>
# TypeError: error!
Could you confirm, and/or post an example of what isn't working as you would expect?
Yep, sorry JustinFX. My Fault. After pulling the newest changes we're good to go. Thanks
Awesome! Thanks for following up.
On Wed, Feb 13, 2013 at 1:49 PM, Murphy Randle notifications@github.comwrote:
Yep, sorry JustinFX. My Fault. After pulling the newest changes we're good to go. Thanks
— Reply to this email directly or view it on GitHubhttps://github.com/justinfx/MayaSublime/issues/6#issuecomment-13468698.
Hi! I LOVE the plugin. Thanks so much for writing it. I'm getting stuck on one thing. When I send a command to maya that has a syntax error or a runtime error, Maya will silently swallow the error and fail to respond, rather than printing the error to the console.
In order to get around this I have to go back to the ol' copy paste method to get maya to show the error. Any ideas?