You may have to manually reattach to the debugger from the debugger-chrome if you get disconnected. Both instances of chrome will be autonomous so you can stop/restart them if you wish. pinned-tab-count=1 Run developer-chrome first, then debugger-chrome.
pinned-tab-count=1 debugger-chrome #!/bin/bashĮxport PROFILE=$HOME/debugger-chromium-profileĮxport DISK_CACHEDIR=/tmp/debugger-chromium-profile-cache Applications/Chromium.app/Contents/MacOS/Chromium \ developer-chrome #!/bin/bashĮxport PROFILE=$HOME/develop-chromium-profileĮxport DISK_CACHEDIR=/tmp/develop-chromium-profile-cache
I made two shell scripts, 'developer-chrome' and 'debugger-chrome'.ĭeveloper-chrome is the instance I want to always be observing, debugger-chrome will just sit in my second monitor so I can see console messages and poke developer-chrome when I want. However, there's a nifty trick you can use although if you're not on OSX you'll have to fiddle around a bit to reproduce what I'm doing.
Previously there was a command line flag -always-enable-devtools, doesn't look like there is anymore.
