I have a Ruby script like this:
result.each do |k, v| puts "----" puts k v.each {|m| puts "\s#{m}"} end
The point is that the first two lines (of each iteration) have no space before them, but the remaining lines have a space. In Terminal the output starts out like this:
---- String % * +
That is correct. In RubyMate the output starts out like this:
---- String % * +
That's incorrect. Where's my initial space? No matter how many \s I ask for, I never get that many in the output. m.
PS I think I'm also seeing some occasional problems where a lot of puts causes the output to hang, so that I have to close the RubyMate window and get it to stop running. But I'm not able to reproduce reliably so I could be wrong about this.
On 10/29/06 1:00 AM, in article 90212432-82C2-4D52-ACB3-68E08D0CB090@macromates.com, "Allan Odgaard" throw-away-1@macromates.com wrote:
On 29. Oct 2006, at 05:02, Matt Neuburg wrote:
[...] In RubyMate the output starts out like this:
What version of RubyMate?
How would I find out the answer to that question? Pls answer in words of one syllable or fewer. :) I am staring very hard at TextMate but it is not responding by tell me any version numbers of any bundles.
And if you are using the latest (r5323) please paste a code sample that run w/o requiring the rest of your unpublished code ;)
How would it come to pass that I would be running a different version of RubyMate than what's inside TextMate 1.5.3? Again, please speak as if I were a complete idiot. m.
On 29. Oct 2006, at 17:29, Matt Neuburg wrote:
What version of RubyMate?
How would I find out the answer to that question? Pls answer in words of one syllable or fewer. :)
Read the text in the RubyMate output window.
Mine says:
RubyMate r5712 running Ruby v1.8.4 (/opt/local/bin/ruby) >>> untitled
[...] How would it come to pass that I would be running a different version of RubyMate than what's inside TextMate 1.5.3? Again, please speak as if I were a complete idiot. m.
You could have done a subversion checkout -- and the version number of TextMate includes a revision number in parenthesis after the 1.5.3, so you could be running 1.5.3 (1215), which is the latest official release, or 1.5.3 (1305), which is latest “cutting edge” and has seen several changes to RubyMate, amongst other improved handling of whitespace (tabs, etc.) -- which version you want to run is set in Preferences → Software Update.
On 10/29/06 9:28 AM, in article 082B2063-A0AD-406E-B6C1-E8A372F1DF25@macromates.com, "Allan Odgaard" throw-away-1@macromates.com wrote:
You could have done a subversion checkout -- and the version number of TextMate includes a revision number in parenthesis after the 1.5.3, so you could be running 1.5.3 (1215), which is the latest official release, or 1.5.3 (1305), which is latest “cutting edge” and has seen several changes to RubyMate, amongst other improved handling of whitespace (tabs, etc.) -- which version you want to run is set in Preferences → Software Update.
Okay, I tried doing a Software Update and got a mild mess. Now when I run a Ruby script, the RubyMate window ain't pretty any more, and it starts with this scolding:
bash: line 1: selected_theme: command not found cat: /Users/mattneub/Library/Application Support/TextMate/Support/css/webpreview.css: No such file or directory
So I take it that the Software Update process has neglected to provide me with some piece of the puzzle.
So yes, I am now running r5323 of RubyMate, and yes, the spacing problem seems to be fixed, but I'm not playing with a full deck any more.
Further Comments:
* It would be helpful if adequate version information (the build number) were displayed in the Finder.
* It would be helpful if a build with a later build number had a later modification date; my whole backup / sync system depends upon modification dates, so the fact that 1.5.3 (1215) and 1.5.3 (1305) have exactly the same mod date really messes with my life.
* It would be helpful if there were an easier way to see bundle version numbers (e.g. directly). Consider how Photoshop or Safari displays plug-in info, for example.
* It would be helpful if there were an easy way to update just one bundle. In fact I could probably do the subversion thing, but the people whom I am trying to persuade to use TextMate probably could not. (The first approach I tried was the validcode.net GetBundle bundle, but I was frustrated to find that embedded bundles were not among its options.)
m.
On 10/29/06 10:38 AM, in article C16A3520.1A96B%matt@tidbits.com, "Matt Neuburg" matt@tidbits.com wrote:
I am now running r5323 of RubyMate, and yes, the spacing problem seems to be fixed, but I'm not playing with a full deck any more
Okay, I used svn to update to RubyMate r5712 and now all is well. But, as I said before, there are users for whom this approach would not be appropriate.
By the way, here's another comment: in the Help documentation, the /Library application support directory is described as the locus of svn working copies. OMM at least, that is not so; it's the ~/Library application support directory. m.
On 29. Oct 2006, at 19:49, Matt Neuburg wrote:
By the way, here's another comment: in the Help documentation, the / Library application support directory is described as the locus of svn working copies. OMM at least, that is not so; it's the ~/Library application support directory. m.
TextMate reads it from both places.
On 10/29/06 11:19 AM, in article E55D25EF-9922-49AC-B640-82D0078B227E@macromates.com, "Allan Odgaard" throw-away-1@macromates.com wrote:
On 29. Oct 2006, at 19:49, Matt Neuburg wrote:
By the way, here's another comment: in the Help documentation, the / Library application support directory is described as the locus of svn working copies. OMM at least, that is not so; it's the ~/Library application support directory. m.
TextMate reads it from both places.
I didn't say it didn't. I said that the Help documentation doesn't say so. m.
On 29. Oct 2006, at 19:38, Matt Neuburg wrote:
Okay, I tried doing a Software Update and got a mild mess. Now when I run a Ruby script, the RubyMate window ain't pretty any more, and it starts with this scolding:
bash: line 1: selected_theme: command not found cat: /Users/mattneub/Library/Application Support/TextMate/Support/css/webpreview.css: No such file or directory
That would indicate a checkout of the Support folder which is newer than what’s included with r1305.
So I take it that the Software Update process has neglected to provide me with some piece of the puzzle.
Well, if you http://macromates.com/wiki/Troubleshooting/ RevertToDefaultBundles everything works out of the box.
Further Comments:
- It would be helpful if adequate version information (the build
number) were displayed in the Finder.
- It would be helpful if a build with a later build number had a later
modification date; my whole backup / sync system depends upon modification dates, so the fact that 1.5.3 (1215) and 1.5.3 (1305) have exactly the same mod date really messes with my life.
This is what I see, if I Get Info on TextMate in Finder:
I.e. the build number and the modification date corresponding to when r1305 was released.
- It would be helpful if there were an easy way to update just one
bundle. In fact I could probably do the subversion thing, but the people whom I am trying to persuade to use TextMate probably could not [...]
Bundles from the subversion repository are only ensured to work with latest (cutting edge) version of TextMate and the Support folder -- so people should never upgrade to a newer bundle (or Support folder) without also upgrading to Cutting Edge of TextMate -- and as TextMate includes latest release version of the 36 most popular bundles, and Cutting Edge releases are done biweekly or so, people not comfortable with subversion should just switch to cutting edge builds instead of fiddling with Subversion themselves, in order to get on the bleeding edge.
On 10/29/06 11:18 AM, in article 27669F71-FB38-4EB4-B9A0-4A5CB4DECB86@macromates.com, "Allan Odgaard" throw-away-1@macromates.com wrote:
On 29. Oct 2006, at 19:38, Matt Neuburg wrote:
Okay, I tried doing a Software Update and got a mild mess. Now when I run a Ruby script, the RubyMate window ain't pretty any more, and it starts with this scolding:
bash: line 1: selected_theme: command not found cat: /Users/mattneub/Library/Application Support/TextMate/Support/css/webpreview.css: No such file or directory
That would indicate a checkout of the Support folder which is newer than what¹s included with r1305.
That doesn't make much sense to me, since at the time I had no Support folder at all. (Nor any Application Support/TextMate folder, for that matter.) All I did was to download the Cutting Edge build of TextMate using Software Update, just as you told me to do.
So I'm simply saying that for the naïve user, merely doing a software update may not work. It didn't for me.
- It would be helpful if adequate version information (the build
number) were displayed in the Finder.
- It would be helpful if a build with a later build number had a later
modification date; my whole backup / sync system depends upon modification dates, so the fact that 1.5.3 (1215) and 1.5.3 (1305) have exactly the same mod date really messes with my life.
This is what I see, if I Get Info on TextMate in Finder:
I didn't say "If I Get Info". I said, "In the Finder."
I.e. the build number and the modification date corresponding to when r1305 was released.
Correct. But since 1.5.3 (1215) and 1.5.3 (1305) are two different beasts, they should have different mod dates.
- It would be helpful if there were an easy way to update just one
bundle. In fact I could probably do the subversion thing, but the people whom I am trying to persuade to use TextMate probably could not [...]
Bundles from the subversion repository are only ensured to work with latest (cutting edge) version of TextMate and the Support folder -- so people should never upgrade to a newer bundle (or Support folder) without also upgrading to Cutting Edge of TextMate
Fine, thanks for telling me. This information might be welcome in the documentation as well. (The docs make no reference to "Cutting Edge" at all, AFAICT.) By and large, though, my point is that this double method of updating is problematic for people who merely want to update one bundle which, as in the case of RubyMate, was giving trouble. If you don't care about user input on the user experience, fine - ignore it. m.
-
Allan Odgaard -
Matt Neuburg