需要带参数的 Chrome Canary
1 | /Applications/Google\ Chrome\ Canary.app/Contents/MacOS/Google\ Chrome\ Canary --remote-debugging-port=9222 |
还要放在 dock
方法 1
Use Automator to create an application that in effect launches Chrome with command line arguments.
Start Automator and select to create an Application. Double-click Run Shell Script in the Library/Utilities folder and replace the text content — cat — with the following:
1 | open -a "Google Chrome.app" --args -pinned-tab-count=4 |
keep the .app suffix or will break with Parallels
Save anywhere you like.
更换图标
To replace this application’s icon, Get Info on your real Google Chrome, click on the icon on the top left, press Cmd-C, Get Info on your Chrome Automator app, click the icon, and press Cmd-V.
Since it’s a different application, the Dock will display two Chrome applications when it’s running: Chrome, and your Chrome launcher.
方法 2
直接修改默认的启动项目
Edit your application bundle to launch a script instead. This script will start the actual application, adding the command line argument.
Right-click Google Chrome.app and select Show Package Contents. Go to Contents/ and open Info.plist in Property List Editor/Xcode (Apple’s developer tools), or a third party plist editor.
Look for the entry CFBundleExecutable or Executable File. Remember its value (e.g. firefox-bin for Firefox). Replace it with parameterized-app.sh.
Open Terminal and enter the following:
touch /Applications/Firefox.app/Contents/MacOS/parameterized-app.sh
open /Applications/Firefox.app/Contents/MacOS/parameterized-app.sh
An editor for the .sh file will open. Set the contents of the file to:
1 | #!/usr/bin/env bash |
(using the actual executable’s name you removed from Info.plist, adding the desired command-line arguments)
Save and close. In Terminal, enter the following:
chmod +x /Applications/Firefox.app/Contents/MacOS/parameterized-app.sh
Now, close Terminal and move your application (which must not be running right now) to a different folder and back again. This will update Launch Services, otherwise your changes will be ignored and irritate you immensely.
Now, when you open your application, it will actually execute the .sh file, which will in turn launch the actual executable file, sending the command line args along.
It will look and behave like you expect it to, but you will need to repeat this whenever you update your application, as this will generally replace the application bundle and all the changes you made.