07.28.06
Posted in TextMate, ruby/rails at 10:25 pm by Haris
Update: This post now hosts two commands, the second one performing aligning operations.
Another entry by the LGFT project. This time, we’ll create a command that allows you to quickly fill rows in columnar editing mode in TextMate with expressions depending on an ever increasing number. For instance we will be able to easily create this:
Hey t1here
Hey t4here
Hey t9here
Not that you would ever want something like that
Anyway, first we’ll see the command, then we’ll see the three modes of usage it has, and finally we’ll talk about how the command works.
Read the rest of this entry »
Permalink
07.27.06
Posted in Uncategorized at 7:22 am by Haris
Today is a big day for me. I will finally be defending my thesis in 6 hours time. Wish me luck!
It is over, it is done! From now on, you may address me as Dr. Charilaos Skiadas, Ph. D.
That is, assuming the dissertation office is happy with the margins
Permalink
07.24.06
Posted in Uncategorized at 7:01 am by Haris
This (via the MacOSX-TeX mailing list) is perhaps the funniest support document I have come across. Adobe’s proposed remedy for the constantly repeatedly generated console message “Invalid Color” that Acrobat is generating is to open the console file with TextEdit, find each occurence of the “Invalid Color” text, remove those lines and save the console file again. In their own words:
An incompatibility between Acrobat 7.x and Mac OS X v10.4 causes the Console utility to generate multiple iterations of this message in the Console.log file every time Acrobat is the active application.
By clearing all “Invalid color…” entries from Console.log, you reduce the size of the log file, preventing potential system issues that a large log file may cause.
You have to laugh.
Later
Permalink
07.18.06
Posted in TextMate at 10:00 pm by Haris
Another entry brought to you by the LGFT (Little Gems For TextMate) project. This is to spice up your email signatures, or perhaps blog posts, by definitions from The Meaning Of Liff. If you don’t know what that is, go and find out.
Read the rest of this entry »
Permalink
Posted in Mac OS X at 9:26 pm by Haris
I just had a weird experience with Camino today. I was casually checking out The Meaning Of Liff and then decided to save the page source, so that I can do something with all the entries later. Sure I could copy and paste the text, but I decide to instead opt for the “save as…” option. Since I wanted to process the text at the end of the day, I tried giving the file the extension txt. Alas, Camino had a different opinion:

Now, why on earth wouldn’t Camino let me save the file with whatever extension I feel like? It is after all my funeral. It seems Safari demonstrates the same kind of behavior. Is this a general feature of Save Panels I was not aware of?
While we are at it, Camino does have an extremely cool feature I had not realized before: Tell it to save the page as Plain Text, and (yes, you guessed it) it will save it as Markdown! Or at least Markdown-like. +1 for Camino over Safari.
Later
Permalink
« Previous entries ·