I have already lost my colors when moving to Lion on my Terminal.app, the same happened when I moved to Mountain Lion, but oh surprise, the fix I found out for Lion didn’t work for Mountain Lion, because in Mountain Lion there is no xterm-color available as a choice of terminal type. The solution I found was to manually edit the configuration options of Terminal.app and so far it seems to work.
You will need (most probably) XCode installed in order to edit the config file which is a plist. You can find the config file in ~/Library/Preferences/com.apple.Terminal.plist. Since the ~/Library folder has been hidden since Lion, your best bet is to open up terminal and type:
which will open the Preferences folder in Finder and you can just find the config file and open it.
Before doing any edits you should quit Terminal, as it saves its settings on exit and it will override any changes you do.
To add the xterm-color option you’ll have to go to Root > Window Settings locate the name of your default theme (in my case that’s Pro) expand it and find the TerminalType key. Now just change the key to xterm-color, save the file and launch Terminal.
As I’ve always strived to automate my home, as much as I can. Although I can’t still turn the lights on and off, I’m capable of controlling my TV, my set-top-box and my multimedia PC with my iPhone. And the problem with the lights is not so much of “impossible” but rather I don’t feel like tearing down my laws to run cables. I actually managed to write an app for a friend to turn his garden lights on and off with his iPhone.
For that purpose, having my TV remote is essential! Unfortunately, after I upgraded my iPhone 3Gs to 4s, the Samsung Remote app started crashing on each launch. Here’s how I managed to get it working:
- Turn off Wi-Fi and cellular data
- Start Samsung TV
- Go into Demo Play
- Turn back on your Wi-Fi
- Hit refresh
- Select a TV from the list
Since WordPress updated their iOS app to include location for posts, it came to my attention that it is fairly easy to add location to your posts – and it works nicely with the “Quick Photo” feature of the iOS WordPress app.
Unfortunately after I installed the WordPress GeoLocation plugin OnSwipe’s iPad theme stopped working for me. After some digging it turned out it is because Geolocation is overwriting the default alias of $ of jQuery which was breaking OnSwipe.
Here is how to fix that:
- Go to your admin panel
- Go to Plugins -> Editor
- In the drop-down Select plugin to edit choose “Geolocation”
- From the file list Plugin Files (just underneath the drop-down) select geolocation/geolocation.php
- Find in the code the function add_google_maps (use your browser’s search function and look for “function add_google_maps”)
- Find the line that reads:
var $j = jQuery.noConflict();either comment it out by prepending two slashes in front of it or delete it
- In its place add the following:
$j = jQuery;
- Click Update File
This should fix OnSwipe and at the same time allow your visitor to view the location tag of your posts!
Ubuntu 11.10 is out! So the package manager prompted me to upgrade from Ubuntu 11.04 and so I did. The upgrade process took several hours, but mainly because I wasn’t paying attention and I didn’t take immediate action of different prompts regarding the upgrade process.
I decided to keep all of my config file modifications hoping that would give me less headache at the end. Nevertheless, I got several problems after I booted in my new shiny Oneric Ocelot (Ubuntu 11.10’s codename).
- I couldn’t go past the login screen – the solution was simple – for some reason my ~/.Xauthority file was owned by root:root – I simply deleted the file and that fixed it
- I didn’t get any sound in Unity, but only in Unity as it turns out, as aplay was playing sound just fine. The sound preferences’ Hardware tab was also completely empty. I deleted the ~/.pulse folder and re-logged and I could re-configure my sound. Sound was back on!
When I upgraded to Lion suddenly my colorful SSH prompts on remote linux machines became dull and black and white. It took me some time to figure out what was going out, so at first I edited my Ubuntu .bashrc file and uncommented
force_color_prompt=yes. But this didn’t seem right. So after some digging I found the problem – in Snow Leopard Terminal.app by default was identifying itself as xterm-color, but now in Lion it is xterm-256color, which the remote Ubuntu did not recognize. So to fix it without changing anything on the remote machines, do the following:
- Open Terminal.app Preferences
- Go to the Settings tab
- In your default theme go to the Advanced tab
- On the first line Declare terminal as: select xterm-color, instead of the default xterm-256color
- Reopen Terminal.app and voilà – the colored SSH command prompt is back!