Since I installed the latest beta, my ruby output is showing up in a new window titled "Ruby TextMate Runtime". By and large, it's better than the command output, except that it appears to be using HTML to render it, so when I'm writing debugging output of XML processing I can't see most of what's been processed.
For example, the Ruby command: puts "<foobar>Hey!</foobar>"
is showing up in the window as: TM-Ruby v0.2 running Ruby v1.8.2.
/Users/gkistner/Desktop/tmp.rb
Hey!
How can I get TextMate not to use the HTML window, or escape my output to that window?
On 04/09/2005, at 1.34, Gavin Kistner wrote:
For example, the Ruby command: puts "<foobar>Hey!</foobar>"
is showing up in the window as: TM-Ruby v0.2 running Ruby v1.8.2.
/Users/gkistner/Desktop/tmp.rb
Hey!
How can I get TextMate not to use the HTML window, or escape my output to that window?
I fixed this quite recently, so you can checkout the latest version of that bundle from the repository. Please see the Wiki for instructions on how to do this. The latest version escapes everything properly and also captures input nicely.
-- Sune.
On 04/09/2005, at 2.30, Sune Foldager wrote:
How can I get TextMate not to use the HTML window, or escape my output to that window?
I fixed this quite recently, so you can checkout the latest version of that bundle from the repository [...]
You may also wait for next TM -- I have on my short-term to-do that I should setup a change log feed with “nightly builds”. So this may appear within a few days.
On Sep 3, 2005, at 6:30 PM, Sune Foldager wrote:
I fixed this quite recently, so you can checkout the latest version of that bundle from the repository. Please see the Wiki for instructions on how to do this. The latest version escapes everything properly and also captures input nicely.
Thanks, that fixed that issue :)
Now, there is one more thing...the output of unit tests is showing up without line breaks in the HTML window:
require 'test/unit' class Foo < Test::Unit::TestCase def test1; assert_equals( 1, 2 ); end def test2; assert_equals( 2, 2 ); end def test3; assert_equals( 3, 2 ); end end
Produces: Loaded suite /Library/Application Support/TextMate/Bundles/ Ruby.tmbundle/Support/tmruby Started F.F Finished in 0.016463 seconds. 1) Failure: test1(Foo) [/Users/gkistner/Desktop/tmp.rb:3]: <1> expected but was <2>. 2) Failure: test3(Foo) [/Users/gkistner/ Desktop/tmp.rb:5]: <3> expected but was <2>. 3 tests, 3 assertions, 2 failures, 0 errors
Instead of: Loaded suite tmp Started F.F Finished in 0.013374 seconds.
1) Failure: test1(Foo) [tmp.rb:3]: <1> expected but was <2>.
2) Failure: test3(Foo) [tmp.rb:5]: <3> expected but was <2>.
3 tests, 3 assertions, 2 failures, 0 errors
Should I simply not be using the HTML window, and using the 'normal' output window instead?
On 05/09/2005, at 2.12, Gavin Kistner wrote:
Now, there is one more thing...the output of unit tests is showing up without line breaks in the HTML window [...]
Ok, I'll look into it.
Should I simply not be using the HTML window, and using the 'normal' output window instead?
The idea is to use RubyMate as it is, i.e. with the HTML window. If you select normal window, you get tons of HTML output instead. I will try to fix this problem :-).
-- Sune.
-
Allan Odgaard -
Gavin Kistner -
Sune Foldager