Fixing Home and End buttons in Mac Terminal

I hate it when Terminal in my mac scrolls up when I hit 'Home' key, or all the way to the bottom, when I hit 'End' key. As most would do, I expect 'Home' key to take me to the beginning of the line, and 'End' to the end of it.

I can of course use 'control+a' and 'control+e' to do that, but it's tough to beat muscle memory.

There is a Stack Exchange 'Ask Different' entry for this, but the keys mentioned there for terminal were not working for me: https://apple.stackexchange.com/questions/16135/remap-home-and-end-to-beginning-and-end-of-line

What seems to work for me is:
* \033[H -> Home
* \033[F -> End

These can be set from Terminal > Preferences > Keyboard as shown in the screenshot. Enjoy!

How to install iOS7 Beta on iPhone 5

I have captured some screenshots but do not have time to upload them yet. Upgrade process is pretty much the same as before:

• Download iOS 7 Beta from developer.apple.com > iOS Downloads (You need to have iOS Developer Account with Apple to get there) Protip: Use Safari on Mac, if possible. For whatever reason, when I used Chrome on my mac, it would just direct me to 'maintenance' page, which said 'We'll be back soon'.
• Open up the downloaded dmg and extract the .ipsw file on to your desktop
• Launch iTunes & Connect your iPhone (Supported models iPhone 4, 4S, 5)
• Click on  your device name and make sure to back it up (on iCloud)
• You can also do a backup on your iPhone using Settings > iCloud menu.
• Once done, click Option Key (Alt key if you are using PC keyboard) and click Restore on iTunes
• On the File Picker window, click the Desktop on the left and choose the extracted iOS7 file
• All in all this takes about 5mins.
• Once completed, it will try to activate. Your phone needs to be registered in the iOS Dev Portal.

Update 2013-06-19:

After using iOS7 for a week, I rolled back. I worked out most of the annoyances but Google+ kept on crashing and I do use Automatic Backups for my pics. So, I can't wait for months to get it all sorted out.

Here are a couple of notes:

• Updates did not work always. Your would see them but clicking update would not do anything.
• Although I backed up everything to iCloud, most of the settings for apps did not come back I had to enter username/pwd for many apps as if just installed.
• Google Authenticator was one of the apps where I lost data and I had to move all 2 factor authentication accounts using 'moving to new iphone' menu. Facebook two-factor authentication is easy to move as well.

iPhone dead...and back

Today, all of a sudden, the screen of my AT&T iPhone 4S went black and it stopped responding. Hitting home button or pressing and holding 'power' button did not help. I connected it to a power source hoping somehow it just needed some juice yet there was no sign of charging animation on the screen, it was dead.

Then, my colleague suggested the following:

Try putting it in DFU mode to at least see if you can restore it. See instructions below.

1. Plug your device into your computer.
2. Turn off the device.
3. Hold the Power button for 3 seconds
4. Hold the Home button without releasing the Power button for 10 seconds
5. Release the Power Button but keep holding the Home button
6. Keep holding the Home button until you are alerted by iTunes saying that it has detected a device in Recovery Mode

I did and it worked. So, I had my iPhone back but it was as if I just bought it, I had to get my data back as well...

I connected it to iTunes on my Windows 7 x64 and attempted to restore the last backup. I got prompted for the backup password. After entering the password, a process seemed to start but never finished. Instead I kept on getting the following message:
"itunes could not restore the iphone because the iphone was disconnected"

I thought it might have been a bad password, that was not it. Upon entering a different password, iTunes warned me that I had incorrect password.

Then, I wondered if my iTunes was corrupted, that was not it. I downloaded the latest version (10.7.0.21) and chose to fix my version to no avail.

At this point, I was worried that my backup was bad. Instead, it turned out that the fix was to connect the phone to a different usb port. As soon as I switched the usb port, restore started to progress and I got   my settings back.

Restoring did not bring my applications back, but that's easy to fix by choosing the apps to install after launching 'App Store' > 'Updates' > 'Not on This iPhone'

Do typos bother you?

Typos do bother me. I guess that's because when I am reading something, they hit (and hurt) my eyes pretty quickly (so if you are seeing typos on this blog, you know why: I do not read my own blog :) and it sort of gives the impression that the person who was writing it may not have paid enough attention to the piece, somewhat decreasing the over all value of it.

Anyway, today I was looking at my Google Reader RSS subscriptions and noticed a new article from Microsoft KB here: "Configuring WinRM for HTTPS" (click on pic above to see the actual page).

There is nothing special about this KB other than that it is on its 8th revision (wow!) as of May 17, 2012, yet apparently information was printed without going through a spell-checker. In fact, there is a note at the bottom of the article which prepares us for such typos:

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice.

I sent a message to them using the feedback system at the bottom. I wonder how long it will take them to correct it.

Update: 2012-06-29
Almost the same story but this time, it's about an Apple Knowledge Base article. Here is a very common typo in article about 'Apple Thunderbolt to Gigabit Ethernet Adapter: FAQ' (HT5309) that was last modified 10 days ago (click on picture to see the actual page).

Unfortunately, there is no feedback mechanism on the page to tell Apple about this.
Oh, Microsoft page is still not corrected. I guess they are not reading the feedback.