Hi,
I'm using the latest version (2.0-alpha.9529) and I've some problems getting python output when running the script.
The python script is just:
print "ok"
It works fine when ran in terminal (Run Script (Terminal)) but if I run script directly (Run Script), I get no output. For other type of files (Latex for example), everything seems ok.
The weirdest part is that if I do the same with another user (administrator) it works fine and I get the output in the window: from my regular account, I can "su administrator" and starts TM from command line and it works as expected.
I tried to reinstall TM, not load my .profile/.bashrc in case something's wrong in my path, delete any TM preferences (com.macromates.TextMate.preview and Library/Caches/...) but it does no change anything.
So I guess something wrong's with my regular account but I'm out of ideas at this point. (I also checked "env" gives same values for regular/administrator)
If someone has any idea ... or how to debug.
Nicolas
On 9 Apr 2014, at 17:04, Nicolas Rougier wrote:
[…] if I run script directly (Run Script), I get no output.
What does “no output” mean? Is the action a no-op, i.e. no windows showing?
If so, try Preferences → Bundles and uncheck/check the Python bundle.
There is an issue with updating bundles (in current release build) where if TM is terminated while updating a bundle, it can leave a broken bundle on disk (partially deleted), which could manifest itself as some actions being no-op (although deleting ~/Library/Caches should have made deleted actions disappear from the menu).
The window output is not showing while the script is ran (I'm opening a GL window from the script and this window is displayed). The problem only occurs for my regular account (/Users/rougier) and not for the others (/Users/administrator). This let me think it is a problem on my side, like a forgotten or hidden settings somewhere but I'm bit clueless.
Also, if I change the mode to "Ruby" for example (same script: print "ok"), I get the output. This seems to be very specific to python (version is 2.7.6).
I tried the uncheck/check with no change. (Even tried before to remove/donwload/reinstalli TM with no change as well)
Nicolas
On 09 Apr 2014, at 12:44, Allan Odgaard mailinglist@textmate.org wrote:
On 9 Apr 2014, at 17:04, Nicolas Rougier wrote:
[…] if I run script directly (Run Script), I get no output.
What does “no output” mean? Is the action a no-op, i.e. no windows showing?
If so, try Preferences → Bundles and uncheck/check the Python bundle.
There is an issue with updating bundles (in current release build) where if TM is terminated while updating a bundle, it can leave a broken bundle on disk (partially deleted), which could manifest itself as some actions being no-op (although deleting ~/Library/Caches should have made deleted actions disappear from the menu).
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
On 9 Apr 2014, at 18:02, Nicolas Rougier wrote:
The window output is not showing while the script is ran (I'm opening a GL window from the script and this window is displayed).
So the script is being executed (i.e. you can see the side-effects of running the script), but TextMate does not indicate that anything is being executed (i.e. no window opens to show the script’s textual output), correct?
Try look in Console for a potential exception and/or https://github.com/textmate/textmate/wiki/Enable-Logging
Also do try (re)move ~/Library/Application Support/Avian and ~/Library/Application Support/TextMate (and then relaunch). The former would contain local changes made to bundles. Like in theory the above could happen if the Python → Run command had its output option changed from New Window to Discard.
Thanks a lot ! Things are back to normal. There was a python bundle in Avian directory.
For the records, I had to remove:
~/Library/Application Support/Avian ~/Library/Application Support/TextMate ~/Library/Preferences/com.macromates.TextMate.preview.LSSharedFileList.plist ~/Library/Preferences/com.macromates.TextMate.preview.plist ~/Library/Caches/com.macromates.TextMate ~/Library/Caches/com.macromates.TextMate.preview
(Only suppressing Avian and TextMate resulted in "CMD-R" in erasing the whole buffer).
Nicolas
On 09 Apr 2014, at 13:11, Allan Odgaard mailinglist@textmate.org wrote:
On 9 Apr 2014, at 18:02, Nicolas Rougier wrote:
The window output is not showing while the script is ran (I'm opening a GL window from the script and this window is displayed).
So the script is being executed (i.e. you can see the side-effects of running the script), but TextMate does not indicate that anything is being executed (i.e. no window opens to show the script’s textual output), correct?
Try look in Console for a potential exception and/or https://github.com/textmate/textmate/wiki/Enable-Logging
Also do try (re)move ~/Library/Application Support/Avian and ~/Library/Application Support/TextMate (and then relaunch). The former would contain local changes made to bundles. Like in theory the above could happen if the Python → Run command had its output option changed from New Window to Discard.
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
-
Allan Odgaard -
Nicolas Rougier -
Nicolas Rougier