On Wed, Jun 17, 2009 at 3:10 PM, Mark Mentovai <[email protected]> wrote:
> Here's what I'm doing: I'm starting my long-lived Chrome (in my case, > an official Google Chrome dev-channel build - ideally it shouldn't be > the executable/bundle you're actively working on) with an alternate > profile by telling my shell to do this: > > /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome > --user-data-dir=~/Library/Application\ Support/ChromeToo >& chrome.out > & > > leaving the "main" profile at ~/Library/Application Support/Chrome > free for development. (You could easily do it the other way around, > but since I'm more likely to want to start the "development" Chromium > more frequently, I figure I'll save myself some keystrokes.) This is exactly how I've run Chrome as my main Windows browser for a year and a half now. Recommended! I think it would be a great idea for everyone developing for the Mac > to join me in eating our dogfood. When we pushed us Windows folks to do this (long ago now...) it really helped close the feedback loop. PK --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
