More > JRiver Media Center 32 for Mac

Links: Opening External Program

<< < (7/7)

MrBiff:
I just tried this:


--- Code: ---<Link version="1.2">
<Item Name="Name">/bin/ls</Item>
<Item Name="Action">0</Item>
<Item Name="Base URL"/>
<Item Name="Search URL"/>
<Item Name="Type">1</Item>
<Item Name="Program Path">/bin/ls</Item>
<Item Name="Program Parameters">"-l" "[Filename]"</Item>
<Item Name="Filter"/>
</Link>
--- End code ---

but get no output in the Terminal that is launched.  Do you?

bob:

--- Quote from: MrBiff on February 02, 2024, 09:49:25 am ---I just tried this:


--- Code: ---<Link version="1.2">
<Item Name="Name">/bin/ls</Item>
<Item Name="Action">0</Item>
<Item Name="Base URL"/>
<Item Name="Search URL"/>
<Item Name="Type">1</Item>
<Item Name="Program Path">/bin/ls</Item>
<Item Name="Program Parameters">"-l" "[Filename]"</Item>
<Item Name="Filter"/>
</Link>
--- End code ---

but get no output in the Terminal that is launched.  Do you?

--- End quote ---
I see the output on Standard Out. Not in a terminal.
I haven't found a way to make the Terminal App run a command line.

You might look at this thread. I played around with some of it.
https://superuser.com/questions/16750/how-can-i-run-an-application-with-command-line-arguments-in-mac-os

bob:

--- Quote from: bob on February 02, 2024, 11:15:54 am ---I see the output on Standard Out. Not in a terminal.
I haven't found a way to make the Terminal App run a command line.

You might look at this thread. I played around with some of it.
https://superuser.com/questions/16750/how-can-i-run-an-application-with-command-line-arguments-in-mac-os

--- End quote ---
There was an issue with paths that will be fixed in the next build. With the fix I can make this work:
Command
/usr/bin/open
Args
"-n" "-a" "/System/Applications/Utilities/Terminal.app" "--args" "/bin/ls"
for example.
However Terminal doesn't seem to accept more than one arg with --args. I can't find a way to make it do something like
/bin/ls -l
Even from just a terminal session.
At any rate this may not affect your use case.
Note also that you can use /usr/bin/open with an app bundle name instead of the path if you specify -b bundlename instead of -a apppath which with the current build would allow you to avoid the slash path issue.

MrBiff:
Nice.  Thank you!

bob:

--- Quote from: MrBiff on February 06, 2024, 07:13:08 pm ---Nice.  Thank you!

--- End quote ---
Great, thanks for the report.

Navigation

[0] Message Index

[*] Previous page