Archive for mac
This post does not show a successful outcome in case that’s what you where hoping for.
I was trying to get OpenBSD bootstrapped using the PXEBoot NIC in a server. I decided to use my Mac which has tftp and bootpd installed. This post is quite in depth and technical so if you are game then read on.
Read the rest of this entry »
I love the new MacBookPro, but the trackpad clicks so loud that people on public transport stare at me. I’m not the only one with the issue.
An enterprising user on the Apple Discussion forums remembers a similar problem and fix for the trackpad from earlier MacBook models. The fix in this case involves removing your battery and sticking a piece of paper between the pad and the chassis. It works, and here is my solution captured at the moment of repair:

Enjoy.
So you have a pattern you want to match across multiple lines, and you have a regular expression that matches it.
You will probably be used to doing this in perl like this:
/some.+?stuff/s
or using regex in ruby like this:
/some.+?stuff/m
However you have just started to get used to Textmate as an editor and you see it supports regex matching. Why though does it not use /s or /m for multi-line dot matching? The reason is that Textmate uses the Oniguruma regular expression library. Oniguruma requires switching to multi-line mode by using an extended group (?m:) so the dot matches the new line as well. So our pattern would be:
(?m:some.+?stuff)
Essentially doing this turns multi-line on for the sub-expression, being some.+?stuff
Make sense? I thought not. Read on about Textmate Regex for more information.
June 26, 2008 at 20:06 · Filed under apps, mac
Forgive my triple Post Hiccup. When Textmate posted my blog posts, I got errors.
Thinking the post had not completed, I retried until I figured out the problem.
If you use WordPress V2.3 and post with Textmate, then don’t try to add a new category when posting an article. You get this problem:
Fatal error: Cannot use object of type WP_Error as array in wp-includes/taxonomy.php on line 1010
Looks like I am not the only one.
« Previous entries ·
Next entries »