Skip to main content

Fix Default Search in Chrome to Use google.com Rather Than Localized Google

I set up a new computer recently, and after installing Chrome, I was incredibly frustrated that searching from the address bar went to google.co.kr rather than google.com, presumably because of IP-geolocation. Took awhile to figure out how to fix it, but here's what you do:

1. Click the wrench, go to Preferences.
2. In "Basics", "Default search", click "Manage".
3. Add a new entry:

Name: Google.com
Keyword: google
URL: http://www.google.com/search?q=%s

Name and keyword can be whatever, the important part is the URL. Then set this as the default, and you're good to go. If you want, you can copy all the other URL params and stick those in the URL too, but it's not critical.

This is also explained here, but it's kinda annoying that it involves this manual tweaking that most people won't know how to do.

Comments

Popular posts from this blog

Why Korean Is Hard For Native English Speakers

A couple of days ago, as an experiment, I wrote my first blog post ever in a non-English language. It was an attempt to explain some of the reasons that Korean is hard to learn for native English speakers, so I figured I might as well try to write it in Korean. Those of you who actually read Korean can see how awkward the attempt was =).

In any case, the post came from an email conversation I had with The Korean from Ask a Korean, a fantastically well-written blog about all things Korea from the perspective of a Korean who moved to the United States during high school. Since I tend to geek out on language things, I figured I might as well post part of that conversation. An edited version follows.

---------

Out of the languages that I've attempted to learn so far, Korean has been the hardest. I've done a lot of meta thinking about learning Korean, and I think there are a number of reasons it's difficult for non-Koreans (and especially Westerners) to learn:

1) Obviously, the…

Stuttering in Korea

I had given up on English. It's my native language, but I figured after 30 some-odd years of disfluent speech, it was time to try something else. So I signed up for language classes in Korean, rationalizing that if I was going to try to teach myself how to speak, I might as well learn a new language along the way.

This might seem completely insane, but when the prevailing theme of your conscious thoughts for multiple decades is some variant of "Why can't I say what I want to say?", you come up with lots of crazy ideas.

For background, I've been a person who stutters for my entire life. I wrote about it on this blog a few years ago, so I think it's time for a followup. I've learned a lot since then, about myself and about stuttering, but in this post I simply want to give some insight into what it's actually like to stutter, and how my speech has changed over time.

After the last stuttering post, the predominant reaction I got from friends was either &…

The King's Speech (and me)

Tonight, I finally gathered the courage to watch The King's Speech. Why did I need courage to watch a movie, you might ask? The reason is both simple and intricately complex:

I'm a stutterer (Edit: person who stutters; "stutterer" is not who I am, but something that I do from time to time), and I have been for as long as I remember.

Well, there it is - I've said it. To be fair, I actually don't remember stuttering when I was little. My first very distinct memory of stuttering was sometime in seventh grade, when I had trouble saying "nosotros" (we/us) in Spanish class. But I also remember knowing I was going to have trouble saying it, because we were going around the room, and I counted ahead to see what I was going to have to say. Which means by that point I was already stuttering. When did it start? That's a question for another day.

So why am I publicizing this fact now? First, I'm in the midst of a lifelong attempt to "cure" my …