A weblog about TextMate, the Universe, and Everything
Wanted to hack TextMate by creating new commands, but didn’t know how because you don’t know any scripting languages or how to do magic using the shell? Fear not, this post will show you all (or at least a small fraction of all) you need to know to use Ruby to write new and wonderful commands. No prior knowledge of Ruby is assumed.
IMPORTANT UPDATE: The GTDAlt bundle now lives in the Subversion Repository of Bundles for TextMate. You can find details on how to access bundles this way here. The version on my website linked to below will NOT be updated any more.
I apologize for the inconvenience to those of you not using subversion, but I can assure you that following the above instructions is pretty painless, and the benefits to my sanity and general state of mind are too numerous to list here.
This is a general help file for the GTDAlt bundle, one of the two bundles for implementing GTD in TextMate. You can also access this file from within the TextMate bundle. This file consists of three parts. The first part is an introduction to the bundle, describing how to use it. The second describes its internals, describing how to extend the bundle. The third is an example of creating a new command.
You can also find some pretty lame screencasts here, as well as a converter to convert your Kinkless GTD project to this format here.
This post has gotten a bit longer than expected, so a quick summary is in order here: If you run Ruby 1.8.2 or earlier, be very careful about using rational.rb and mathn.rb. The algorithms in there for computing the gcd of numbers, necessary in almost every operation, are from kind of bad to utterly horrible, and in particular in one of my projects 30% of the program time was spent in computing gcds.
Ok, and now for our feature presentation:
Read the rest of this entry »
Now that the new MacBooks are out, I am tempted more and more to get a new laptop. But after all the trouble that Daniel Jarkut has been going through, and seeing the huge percentage of people who seem to be having problems with their MacBook Pros, I think I’ll have to wait a bit longer and see. I have to say that Apple’s stand on this matter mystifies me. They seem to claim that the whine and the heat and all that is “within specs” and not really an issue, but from the reports I am seeing I just don’t buy it. I’d love to get my hands on one of those noisy babies, just to see how irritating it is.
Update: Pierre Igot seems to be having similar problems, and in fact with a MacBook, and is quite unhappy about it. He is returning the machine and, to add insult to injury, he found out that he will have to pay a 10% restocking fee because his computer was “custom made”, i.e. had some RAM added! Initially they were actually refusing to take it back at all!! Are you listening Apple? This kind of treatment is unacceptable, and it hurts the company’s reputation. I better start looking for a different gift to myself for when I finish my thesis….
Update 2: Good news for Daniel
Later
I have very weak wrists, and consequently I have tremendously appreciated the feel of the keys on my iBook, and I can’t stand typing on the big apple keyboard in my office desktop. So now that I am thinking of getting a desktop computer for my office at my new home, I need to find a keyboard that is close enough. It is an absolute requirement that it has a short key travel time, the keys are easy to press, and that the function keys are easily within reach, and preferably on both sides. My current two candidates are the Kensington Slim Type and the Macally iceKey, and I would also consider the much cheaper ikeyslim if I could find any reviews of it. Right now I am leaning on the iceKey.
Any thoughts or suggestions?
Later
| M | T | W | T | F | S | S |
|---|---|---|---|---|---|---|
| « Feb | ||||||
| 1 | 2 | 3 | ||||
| 4 | 5 | 6 | 7 | 8 | 9 | 10 |
| 11 | 12 | 13 | 14 | 15 | 16 | 17 |
| 18 | 19 | 20 | 21 | 22 | 23 | 24 |
| 25 | 26 | 27 | 28 | 29 | 30 | 31 |