BigDiver

Hi I feel that this  a prety common request: Bind the Home/End keys to move to the beginning and end of lines respectively.

In Mac OS X (10.5 and 10.6) some applications use the Cmd-Rigt and Cmd-Left to perform these actions but, call me old fashioned, I like to use Home and End instead.

It is actually very easy to change the Cocoa Key bindings for any user under Mac OS. Just follow these steps:

1. Create a file called DefaultKeyBinding.dict in ~/Library/KeyBindings directory

   mkdir ~/Library/KeyBindings
   cd ~/Library/KeyBindings
   touch DefaultKeyBinding.dict

2. Edit your DefaultKeyBinding.dict file so it contains:

   {
   /* home */
   "\UF729"  = "moveToBeginningOfLine:";
   "$\UF729" = "moveToBeginningOfLineAndModifySelection:";
   
   /* Cmd-Left */
   "@\UF702"  = "moveToBeginningOfLine:";
   "$@\UF702" = "moveToBeginningOfLineAndModifySelection:";
   
   /* Cmd-Right */
   "@\UF703"  = "moveToEndOfLine:";
   "$@\UF703" = "moveToEndOfLineAndModifySelection:";
   
   /* end */
   "\UF72B"  = "moveToEndOfLine:";
   "$\UF72B" = "moveToEndOfLineAndModifySelection:";
   
   /* page up/down */
   "\UF72C"  = "pageUp:";
   "\UF72D"  = "pageDown:";
   }

3. Restart the Cocoa Application.

This example works very well with TextMate.

In order to bind other keys you need to find their Scan code, and you can use the following modifiers
For more information please check this article

I have to say that my experience upgrading both my Macs to Snow Leopard has been mixed. It was easy as clicking the Install button on the iMac, it was a nightmare on the Macbook Air.

First I used the Remote CD installation process, started the Macbook Air, mounted the remote CD from the iMac and proceeded to run the “Install Mac OSX.app”. After agreeing to the license agreement the installation utility told me that the disk did not have enough free space. Despite the fact that the disk had 21Gb of free space!

After some digging I found out that PGP Whole Disk Encryption is not compatible with Snow Leopard, and PGP advised users to decrypt the disk before upgrading.

So I decrypted the disk and restarted the Installation process, only to find out a new error! Damn.

The install app now told me that the Machintosh HD, the only disk, in my Macbook Air, was not a bootable disk and could not install to it. I did some more web searching and some people reported the error to related to the partition format, not being GUID.

I checked with Disk Util and it was indeed GUID. So using Disk Util I added a new partition with 1Gb, using the free space, this procedure rewrote the new partition table to disk and after I was able to finally install Snow Leopard.
When Snow Leopard was installed I used Disk Util again to delete the 1Gb partition and recover the disk space.

If Disk Utility gives you disk verification errors, you need to repair those before resizing your partitions. If you repair the disk multiple times and it still gives you the same errors then you should run the Remote Install Mac OS X application on another Mac. If you only have a Windows as a second computer check this the “How to use Remote Disc” article on Apple’s support site.

Boot your MacBook Air directly into the Snow Leopard CD. Just start the Air and hold the option key until you see the list of disks you have to boot from. If the Remote Install Mac OS X application is running on your other computer the Snow Leopard will show up here.

Have you had Snow Leopard upgrade issues?

Finally I got my iMac backing up to the TeraStation using Time Machine by following the instructions on this site.

The trick was creating the Sparse file by hand, after enabling the use of network volumes. I am using AppleTalk to mount the TeraStation share for the backups, and I setup a different share just for the backup files.

If the file “com.apple.timemachine.supported” does not get created automatically by Time Machine you’ll have to create it yourself.

Some sites discourage the use of SMB, all I can say is that the referenced procedure only worked for me with AFP. Maybe your mileage will vary.

Great job Newb @ MacTimes!
Thanks!

While configuring Apache on my MAC Leopard I ran into Forbidden 403 errors while accessing the ~user/ directory. Read a ton of posts and Apple forums but in the end what got it fixed was a post by Ricardo at Mutantur

chmod 701 ~
chmod 705 ~/Sites

Thanks Ricardo!

When running Outlook 2007 inside Parallels in MAC OS Leopard, I could not send email. If I used the “Test Account Settings” in when configuring my email account Outlook sent the email and said all was ok, but when trying to send regular email from the Outbox everything was not ok and no email was going out. I could not send email no matter what changes I tried in Outlook. 

Tested the connectivity with the mail server using telnet and Thunderbird and all worked fine. So the problem was in Outlook it self.I then downloaded DRTcp and configured the MTU to 1492. After a reboot all email was going out with no problems! 

If Microsoft Outlook chases you even in your MAC, and you can receive email, but cannot send this may help you.