blocks|key|1258111|text|在OS+X+10.6中，open命令得到了增强，允许向应用程序传递参数：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1258112|open+./AppName.app+--args+-AppCommandLineArg|code-block|syntax|javascript|1258113|但对于Mac的老版本，由于应用程序包不是为传递命令行参数而设计的，因此传统的机制是对文件使用Apple+Events，如用于可可应用程序的here或用于碳排放应用程序的here。您还可以通过使用环境变量传递参数来做一些杂乱无章的事情。|1258114|entityMap|0|LINK|mutability|MUTABLE|url|https://developer.apple.com/legacy/library/documentation/Darwin/Reference/ManPages/man1/open.1.html|1|https://en.wikipedia.org/wiki/Apple_event|2|https://developer.apple.com/library/content/documentation/Cocoa/Conceptual/ScriptableCocoaApplications/SApps_handle_AEs/SAppsHandleAEs.html|3|https://developer.apple.com/legacy/library/documentation/AppleScript/Conceptual/AppleEvents/intro_aepg/intro_aepg.html^0|C|4|C|4|0|0|0|1A|C|1|1X|4|2|2C|4|3|0^^$0|@$1|2|3|4|5|6|7|10|8|@$9|11|A|12|B|C]]|D|@$9|13|A|14|1|15]]|E|$]]|$1|F|3|G|5|H|7|16|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|17|8|@]|D|@$9|18|A|19|1|1A]|$9|1B|A|1C|1|1D]|$9|1E|A|1F|1|1G]]|E|$]]|$1|M|3|-4|5|6|7|1H|8|@]|D|@]|E|$]]]|N|$O|$5|P|Q|R|E|$S|T]]|U|$5|P|Q|R|E|$S|V]]|W|$5|P|Q|R|E|$S|X]]|Y|$5|P|Q|R|E|$S|Z]]]]

In OS X 10.6, the <a href="https://developer.apple.com/legacy/library/documentation/Darwin/Reference/ManPages/man1/open.1.html" rel="noreferrer"><code>open</code></a> command was enhanced to allow passing of arguments to the application:

<pre><code>open ./AppName.app --args -AppCommandLineArg
</code></pre>

But for older versions of Mac OS X, and because app bundles aren't designed to be passed command line arguments, the conventional mechanism is to use <a href="https://en.wikipedia.org/wiki/Apple_event" rel="noreferrer">Apple Events</a> for files like <a href="https://developer.apple.com/library/content/documentation/Cocoa/Conceptual/ScriptableCocoaApplications/SApps_handle_AEs/SAppsHandleAEs.html" rel="noreferrer">here</a> for Cocoa apps or <a href="https://developer.apple.com/legacy/library/documentation/AppleScript/Conceptual/AppleEvents/intro_aepg/intro_aepg.html" rel="noreferrer">here</a> for Carbon apps. You could also probably do something kludgey by passing parameters in using environment variables.

blocks|key|1472841|text|正如问题here中提到的，10.6中的open命令现在有一个args标志，因此您可以调用：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1472842|open+-n+./AppName.app+--args+-AppCommandLineArg|1472843|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/1569976/osx-launching-multiple-instances-of-an-app-and-passing-them-command-line-args^0|J|4|U|4|4|4|0|0|0|1B|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]|$9|S|A|T|B|C]]|D|@$9|U|A|V|1|W]]|E|$]]|$1|F|3|G|5|6|7|X|8|@$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|10|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]]]

As was mentioned in the question <a href="https://stackoverflow.com/questions/1569976/osx-launching-multiple-instances-of-an-app-and-passing-them-command-line-args">here</a>, the <code>open</code> command in 10.6 now has an <code>args</code> flag, so you can call:

<code>open -n ./AppName.app --args -AppCommandLineArg</code>

blocks|key|1258017|text|应用程序包(+.app文件)实际上是一堆目录。而不是使用open和.app名称，您实际上可以移到它并启动实际的二进制文件。例如：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1258018|$+cd+/Applications/LittleSnapper.app/
$+ls
Contents
$+cd+Contents/MacOS/
$+./LittleSnapper|code-block|syntax|javascript|1258019|这是实际的二进制文件，它可能接受参数(在LittleSnapper的情况下，也可能不接受)。|1258020|entityMap^0|7|4|S|4|X|4|0|0|K|D|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]|$9|T|A|U|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|V|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|M|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]]|N|$]]

An application bundle (a <code>.app</code> file) is actually a bunch of directories. Instead of using <code>open</code> and the <code>.app</code> name, you can actually move in to it and start the actual binary. For instance:

<pre><code>$ cd /Applications/LittleSnapper.app/
$ ls
Contents
$ cd Contents/MacOS/
$ ./LittleSnapper
</code></pre>

That is the actual binary that might accept arguments (or not, in <code>LittleSnapper</code>'s case).

blocks|key|1472919|text|如果你的应用程序需要处理文件(你通常期望传递为：./myApp+*.jpg)，你可以这样做：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1472920|open+*.jpg+-a+myApp|code-block|syntax|javascript|1472921|entityMap^0|O|D|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|L|$]]

In case your app needs to work on files (what you would normally expect to pass as: <code>./myApp *.jpg</code>), you would do it like this:

<pre><code>open *.jpg -a myApp
</code></pre>

blocks|key|1258606|text|您可以使用open启动应用程序|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1258607|open+-a+APP_YOU_WANT|code-block|syntax|javascript|1258608|这应该会打开您想要的应用程序。|1258609|entityMap^0|5|4|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|S|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|N|$]]

You can launch apps using <code>open</code>:

<pre class="lang-sh prettyprint-override"><code>open -a APP_YOU_WANT
</code></pre>

This should open the application that you want.

blocks|key|1472812|text|我推荐MathieuK提供的技术。在我的例子中，我需要尝试一下Chromium：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1472813|>+Chromium.app/Contents/MacOS/Chromium+--enable-remote-fonts|code-block|syntax|javascript|1472814|我知道这不能解决操作员的问题，但希望它能节省别人的时间。:)|1472815|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I would recommend the technique that MathieuK offers. In my case, I needed to try it with Chromium:

<pre><code>&gt; Chromium.app/Contents/MacOS/Chromium --enable-remote-fonts
</code></pre>

I realize this doesn't solve the OP's problem, but hopefully it saves someone else's time. :)

blocks|key|1258466|text|open还有一个-a标志，你可以用它从Applications文件夹中通过应用程序的名称(或带有-b标志的捆绑包标识符)打开应用程序。您可以将其与--args选项结合使用，以获得您想要的结果：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1258467|open+-a+APP_NAME+--args+ARGS|code-block|syntax|javascript|1258468|要在VLC播放器中打开一个应该以2倍的比例缩放并循环的视频，您可以执行以下操作：|1258469|open+-a+VLC+--args+-L+--fullscreen|1258470|请注意，我无法将命令的输出发送到终端。(尽管我没有尝试解决这个问题)|1258471|entityMap^0|0|4|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|V|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|W|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|X|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|Y|8|@]|D|@]|E|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]]|R|$]]

<code>open</code> also has an -a flag, that you can use to open up an app from within the Applications folder by it's name (or by bundle identifier with -b flag). You can combine this with the --args option to achieve the result you want:

<pre><code>open -a APP_NAME --args ARGS
</code></pre>

To open up a video in VLC player that should scale with a factor 2x and loop you would for example exectute:

<pre><code>open -a VLC --args -L --fullscreen
</code></pre>

Note that I could not get the output of the commands to the terminal. (although I didn't try anything to resolve that)

blocks|key|1472990|text|我希望有两个单独的Chrome实例运行，每个实例都使用自己的配置文件。我希望能够从Spotlight启动它们，这是我启动Mac应用程序的习惯。换句话说，我需要两个普通的Mac应用程序，regChrome用于正常浏览，altChrome用于使用特殊配置文件，通过按⌘-空格键打开Spotlight，然后输入'reg‘或'alt'，然后输入，就可以轻松地启动它们。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1472991|我认为实现上述目标的暴力方式将是在各自的名称下制作两个Google+Chrome应用程序包的副本。但这是丑陋的，并使更新复杂化。|1472992|我最终得到的是两个AppleScript应用程序，每个应用程序都包含两个命令。下面是针对altChrome的示例|1472993|do+shell+script+"cd+/Applications/Google\\+Chrome.app/Contents/Resources/;+rm+app.icns;+ln+/Users/garbuck/local/chromeLaunchers/Chrome-swirl.icns+app.icns"
do+shell+script+"/Applications/Google\\+Chrome.app/Contents/MacOS/Google\\+Chrome+--user-data-dir=/Users/garbuck/altChrome+>/dev/null+2>&1+&"|code-block|syntax|javascript|1472994|第二行使用备用配置文件(+--user-data-dir参数)启动Chrome。|1472995|第一行是为这两个应用程序提供不同图标的失败尝试。最初，它似乎工作得很好。然而，迟早，Chrome会重新读取其图标文件，并获取与两个应用程序中最后启动的应用程序相对应的文件，从而导致两个正在运行的应用程序具有相同的图标。但我并没有费心去解决这个问题--我把这两个浏览器放在不同的桌面上，而且在它们之间导航也不是问题。|1472996|entityMap|0|LINK|mutability|MUTABLE|url|https://en.wikipedia.org/wiki/Spotlight_(software))|1|https://en.wikipedia.org/wiki/AppleScript^0|2K|9|30|9|15|9|0|0|0|18|9|9|B|1|0|0|D|F|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@$9|13|A|14|B|C]|$9|15|A|16|B|C]]|D|@$9|17|A|18|1|19]]|E|$]]|$1|F|3|G|5|6|7|1A|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|1B|8|@$9|1C|A|1D|B|C]]|D|@$9|1E|A|1F|1|1G]]|E|$]]|$1|J|3|K|5|L|7|1H|8|@]|D|@]|E|$M|N]]|$1|O|3|P|5|6|7|1I|8|@$9|1J|A|1K|B|C]]|D|@]|E|$]]|$1|Q|3|R|5|6|7|1L|8|@]|D|@]|E|$]]|$1|S|3|-4|5|6|7|1M|8|@]|D|@]|E|$]]]|T|$U|$5|V|W|X|E|$Y|Z]]|10|$5|V|W|X|E|$Y|11]]]]

I wanted to have two separate instances of Chrome running, each using its own profile. I wanted to be able to start them from <a href="https://en.wikipedia.org/wiki/Spotlight_(software)" rel="nofollow noreferrer">Spotlight</a>, as is my habit for starting Mac apps. In other words, I needed two regular Mac applications, <code>regChrome</code> for normal browsing and <code>altChrome</code> to use the special profile, to be easily started by keying ⌘-space to bring up Spotlight, then 'reg' or 'alt', then Enter.

I suppose the brute-force way to accomplish the above goal would be to make two copies of the Google Chrome application bundle under the respective names. But that's ugly and complicates updating.

What I ended up with was two <a href="https://en.wikipedia.org/wiki/AppleScript" rel="nofollow noreferrer">AppleScript</a> applications containing two commands each. Here is the one for <code>altChrome</code>:

<pre><code>do shell script "cd /Applications/Google\\ Chrome.app/Contents/Resources/; rm app.icns; ln /Users/garbuck/local/chromeLaunchers/Chrome-swirl.icns app.icns"
do shell script "/Applications/Google\\ Chrome.app/Contents/MacOS/Google\\ Chrome --user-data-dir=/Users/garbuck/altChrome &gt;/dev/null 2&gt;&amp;1 &amp;"
</code></pre>

The second line starts Chrome with the alternate profile (the <code>--user-data-dir</code> parameter).

The first line is an unsuccessful attempt to give the two applications distinct icons. Initially, it appears to work fine. However, sooner or later, Chrome rereads its icon file and gets the one corresponding to whichever of the two apps was started last, resulting in two running applications with the same icon. But I haven't bothered to try to fix it — I keep the two browsers on separate desktops, and navigating between them hasn't been a problem.

blocks|key|1258387|text|从OS+X+Yosemite开始，我们现在可以使用AppleScript和Automator自动执行复杂的任务。用于自动化的JavaScript现在可以用作脚本语言。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1258388|可以使用bash和osascript交互模式在命令行中编写的This+page+gives+a+good+example+example+script。它打开一个Safari选项卡并导航到example.com。|style|CODE|1258389|http://developer.telerik.com/featured/javascript-os-x-automation-example/|1258390|osascript+-l+JavaScript+-i
Safari+=+Application("Safari");
window+=+Safari.windows[0];
window.name();
tab+=+Safari.Tab({url:"http://www.example.com"});
window.tabs.push(tab);+
window.currentTab+=+tab;|code-block|syntax|javascript|1258391|entityMap|0|LINK|mutability|MUTABLE|url|https://en.wikipedia.org/wiki/OS_X_Yosemite|1|https://en.wikipedia.org/wiki/AppleScript|2|https://en.wikipedia.org/wiki/List_of_macOS_components#Automator|3|https://en.wikipedia.org/wiki/AppleScript#Script_launchers|4|5^0|1|D|0|P|B|1|11|9|2|0|2M|B|9|9|3|U|19|4|0|0|21|5|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@$A|15|B|16|1|17]|$A|18|B|19|1|1A]|$A|1B|B|1C|1|1D]]|C|$]]|$1|D|3|E|5|6|7|1E|8|@$A|1F|B|1G|F|G]]|9|@$A|1H|B|1I|1|1J]|$A|1K|B|1L|1|1M]]|C|$]]|$1|H|3|I|5|6|7|1N|8|@]|9|@$A|1O|B|1P|1|1Q]]|C|$]]|$1|J|3|K|5|L|7|1R|8|@]|9|@]|C|$M|N]]|$1|O|3|-4|5|6|7|1S|8|@]|9|@]|C|$]]]|P|$Q|$5|R|S|T|C|$U|V]]|W|$5|R|S|T|C|$U|X]]|Y|$5|R|S|T|C|$U|Z]]|10|$5|R|S|T|C|$U|11]]|12|$5|R|S|T|C|$U|I]]|13|$5|R|S|T|C|$U|I]]]]

Beginning with <a href="https://en.wikipedia.org/wiki/OS_X_Yosemite" rel="nofollow noreferrer">OS X Yosemite</a>, we can now use <a href="https://en.wikipedia.org/wiki/AppleScript" rel="nofollow noreferrer">AppleScript</a> and <a href="https://en.wikipedia.org/wiki/List_of_macOS_components#Automator" rel="nofollow noreferrer">Automator</a> to automate complex tasks. JavaScript for automation can now be used as the scripting language.

<a href="http://developer.telerik.com/featured/javascript-os-x-automation-example/" rel="nofollow noreferrer">This page gives a good example example script</a> that can be written at the command line using bash and <a href="https://en.wikipedia.org/wiki/AppleScript#Script_launchers" rel="nofollow noreferrer">osascript</a> interactive mode. It opens a Safari tab and navigates to <code>example.com</code>.

http://developer.telerik.com/featured/javascript-os-x-automation-example/

<pre><code>osascript -l JavaScript -i
Safari = Application("Safari");
window = Safari.windows[0];
window.name();
tab = Safari.Tab({url:"http://www.example.com"});
window.tabs.push(tab); 
window.currentTab = tab;
</code></pre>

blocks|key|1472872|text|使用applescript：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1472873|tell+application+"Firefox"+to+activate|code-block|syntax|javascript|1472874|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

With applescript:

<pre><code>tell application "Firefox" to activate
</code></pre>

blocks|key|1258627|text|当您可以简单地访问应用程序文件夹和类型时，有许多复杂的答案：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1258628|打开-a应用程序名称|1258629|就是这个!|1258630|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Lots of complex answers when you can simply access Applications folder and type:
open -a [APP NAME]
This is it!

blocks|key|1473207|text|为什么不直接设置添加路径到应用程序的bin。对于MacVim，我做了以下工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1473208|export+PATH=/Applications/MacVim.app/Contents/bin:$PATH|code-block|syntax|javascript|1473209|别名是我尝试过的另一个选择。|1473210|alias+mvim='/Applications/MacVim.app/Contents/bin/mvim'
alias+gvim=mvim+|1473211|使用导出路径，我可以调用应用程序中的所有命令。在我的MacVim测试中，参数通过得很好。而别名，我必须给bin中的每个命令加上别名。|1473212|mvim+README.txt
gvim+Anotherfile.txt|1473213|享受别名和路径的强大功能。但是，在升级操作系统时，您确实需要监视更改。|1473214|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|W|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|Y|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

Why not just set add path to to the bin of the app. For MacVim, I did the following. 

<pre><code>export PATH=/Applications/MacVim.app/Contents/bin:$PATH
</code></pre>

An alias, is another option I tried.

<pre><code>alias mvim='/Applications/MacVim.app/Contents/bin/mvim'
alias gvim=mvim 
</code></pre>

With the export PATH I can call all of the commands in the app. Arguments passed well for my test with MacVim. Whereas the alias, I had to alias each command in the bin.

<pre><code>mvim README.txt
gvim Anotherfile.txt
</code></pre>

Enjoy the power of alias and PATH. However, you do need to monitor changes when the OS is upgraded.

blocks|key|1473240|text|很简单，在这里将"+app“替换为您想要启动的应用程序的名称。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1473241|export+APP_HOME=/Applications/APP.app/Contents/MacOS
export+PATH=$PATH:$APP_HOME|code-block|syntax|javascript|1473242|以后再谢谢我吧。|1473243|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Simple, here replace the "APP" by name of the app you want to launch.

<pre><code>export APP_HOME=/Applications/APP.app/Contents/MacOS
export PATH=$PATH:$APP_HOME
</code></pre>

Thanks me later.

I want to launch an app on OSX from a script. I need pass it command line arguments. Unfortunately, <code>open</code> doesn't accept command line args.

The only option I can think of is to use <code>nohup myApp &gt; /dev/null &amp;</code> to launch my app so it can exist independently of the script that launches it.

Any better suggestions?

Launch an app on OS X with command line

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我想在OSX上通过脚本启动一个应用程序。我需要向它传递命令行参数。不幸的是，open不接受命令行参数。我能想到的唯一选择是使用nohup myApp > /dev/null &启动我的应用程序，这样它就可以独立于启动它的脚本而存在。有什么更好的建议吗？

问使用命令行在OS X上启动应用程序
EN

回答 13

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用命令行在OS X上启动应用程序EN

回答 13

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用命令行在OS X上启动应用程序
EN