“which” command doesn't work / path of Safari?Reset your PATH variableIn OSX Yosemite, why can I set many...
The use of multiple foreign keys on same column in SQL Server
How to report a triplet of septets in NMR tabulation?
How is this relation reflexive?
How can bays and straits be determined in a procedurally generated map?
whey we use polarized capacitor?
Why was the small council so happy for Tyrion to become the Master of Coin?
Can I make popcorn with any corn?
How to type dʒ symbol (IPA) on Mac?
"You are your self first supporter", a more proper way to say it
DOS, create pipe for stdin/stdout of command.com(or 4dos.com) in C or Batch?
What typically incentivizes a professor to change jobs to a lower ranking university?
What are these boxed doors outside store fronts in New York?
What is the logic behind how bash tests for true/false?
I probably found a bug with the sudo apt install function
Circuitry of TV splitters
What makes Graph invariants so useful/important?
Motorized valve interfering with button?
Is it possible to make sharp wind that can cut stuff from afar?
Compute hash value according to multiplication method
Work Breakdown with Tikz
A Journey Through Space and Time
GPS Rollover on Android Smartphones
Banach space and Hilbert space topology
Pronouncing Dictionary.com's W.O.D "vade mecum" in English
“which” command doesn't work / path of Safari?
Reset your PATH variableIn OSX Yosemite, why can I set many environment variables for GUI apps, but cannot set the specific variable PATHIn the light of the FREAK TLS vulnerability, how may I disable insecure cipher suites manually in Safari?Adding a directory to $PATH doesn't work in YosemiteA complicated script to automate functions in SafariTerminal command to clear DNS cache doesn't seem to workCommand found with `which` at the new paths but still tries to run from the old pathHow can I move files or directories marked as a backup?mysql on OSX suddenly stopped functioning, unable to locate or connectCommand path for exit
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
Why can’t I locate programs like Chrome or Safari or FireFox with the which
command line tool?
pasocon:~ ThisUser$ which python
/anaconda3/bin/python
pasocon:~ ThisUser$ which firefox
pasocon:~ ThisUser$ which Safari
pasocon:~ ThisUser$ which chrome
pasocon:~ ThisUser$
This is what I get with the which
command. It is not giving me the path for many applications. Am I making a mistake here or is this potentially an issue to be fixed?
Alternatively, I was just looking for the path of Safari (so that you can open Safari by directing to this path in a configuration file). I am sure this is basic knowledge but I've somehow failed to find it.
macos terminal safari command-line path
New contributor
add a comment |
Why can’t I locate programs like Chrome or Safari or FireFox with the which
command line tool?
pasocon:~ ThisUser$ which python
/anaconda3/bin/python
pasocon:~ ThisUser$ which firefox
pasocon:~ ThisUser$ which Safari
pasocon:~ ThisUser$ which chrome
pasocon:~ ThisUser$
This is what I get with the which
command. It is not giving me the path for many applications. Am I making a mistake here or is this potentially an issue to be fixed?
Alternatively, I was just looking for the path of Safari (so that you can open Safari by directing to this path in a configuration file). I am sure this is basic knowledge but I've somehow failed to find it.
macos terminal safari command-line path
New contributor
add a comment |
Why can’t I locate programs like Chrome or Safari or FireFox with the which
command line tool?
pasocon:~ ThisUser$ which python
/anaconda3/bin/python
pasocon:~ ThisUser$ which firefox
pasocon:~ ThisUser$ which Safari
pasocon:~ ThisUser$ which chrome
pasocon:~ ThisUser$
This is what I get with the which
command. It is not giving me the path for many applications. Am I making a mistake here or is this potentially an issue to be fixed?
Alternatively, I was just looking for the path of Safari (so that you can open Safari by directing to this path in a configuration file). I am sure this is basic knowledge but I've somehow failed to find it.
macos terminal safari command-line path
New contributor
Why can’t I locate programs like Chrome or Safari or FireFox with the which
command line tool?
pasocon:~ ThisUser$ which python
/anaconda3/bin/python
pasocon:~ ThisUser$ which firefox
pasocon:~ ThisUser$ which Safari
pasocon:~ ThisUser$ which chrome
pasocon:~ ThisUser$
This is what I get with the which
command. It is not giving me the path for many applications. Am I making a mistake here or is this potentially an issue to be fixed?
Alternatively, I was just looking for the path of Safari (so that you can open Safari by directing to this path in a configuration file). I am sure this is basic knowledge but I've somehow failed to find it.
macos terminal safari command-line path
macos terminal safari command-line path
New contributor
New contributor
edited 57 mins ago
bmike♦
161k46290629
161k46290629
New contributor
asked 14 hours ago
RethliopuksRethliopuks
1133
1133
New contributor
New contributor
add a comment |
add a comment |
4 Answers
4
active
oldest
votes
which
searches for binaries in the $PATH, a.k.a. command-line tools. User applications are not such tools and not available in the command line.
While Google Chrome.app is an application, the chrome
binary is not usually added to the $PATH because it is not a command line tool — if you just run chrome
in Terminal your shell will inform you that the command cannot be found.
To find the path to an application, you can use lsregister, which is a tool for adding and querying the Launch Services database, used by macOS in part to find applications. You can -dump
the database and filter with grep
.
/System/L*/Fr*/CoreSe*/V*/A/F*/L*/V*/A/S*/lsregister -dump |
grep -ie "path:.*safari"
path: /Applications/Safari.app
This will return every instance of Safari registered with Launch Services, which will include backups. If you just want to open Safari, you shouldn't be dealing with getting paths and handling it yourself; instead, get macOS to do that for you: open -a Safari
.
1
As much as I love the wildcards, I worry that someday Apple will add another service with a similar path and break the commands. It would be good to expand the path fully; it also makes it clearer just what’s being executed.
– nneonneo
3 hours ago
@nneonneo I was under the impression that first point wasn’t an issue, since providing the full name of the tool at the end will ensure the correct tool is always found, for example try running/System/*/*/*/*/A/*/*/*/A/*/lsregister
— the path given in the answer will be faster than the path in this comment since the answer provides enough to be unique, but both should work just as well! (‘A’ is preserved in this minimal path since ‘Current’ is symlinked to ‘A’.) I’ll see about grabbing the full path and adding it to the answer if you really think it improves clarity.
– grg♦
3 hours ago
I mean, I just don’t see how a bunch of wildcards is clear at all as to what’s being run. I would much rather see a long, deep path than a bunch of wildcards, and I think that would be a lot clearer.
– nneonneo
2 hours ago
the chrome binary is not usually added to the $PATH because it is not a command line tool
. Uh, well, considering it explicitly supportsheadless
mode, and I have several projects that uses it extensively from the CLI, I have to say I think you're incorrect.
– Fake Name
15 mins ago
add a comment |
This is working as designed.
which is a command line executable that looks on your path (and other parts of shell environment) to find things you can start from the command line
Applications like Safari (anything bundled as an application which will be a directory ending in .app with certain files in specific sub directories) are not launched from the command line. They are launched from the desktop and not via any shell commands.
You can however launch applications from the command line using the command open. man open gives details. The example to launch Safari is open -a Safari
Note that if you are trying to open Safari when you login putting this command in your shell files will not work as the shell is not run until you launch Terminal.app.
The easiest way to launch Safari at login is to run the app from the desktop, right click on the app's icon in the dock and choose Options then Open at Login.
There is also a list of things that are launched at login for each user in System Preferences->Users & Groups and this can be edited there.
add a comment |
On macOS applications aren‘t part of the standard PATH and can‘t be started by calling them from the command line (well, yes, they can, but it‘s not so easy). But you can use
open foo.html
or
open -a Safari
to start Safari from bash.
add a comment |
Add following in your .bash_profile.
alias safari="/Applications/Safari.app/Contents/MacOS/Safari"
You can now start safari in your Terminal. As mentioned before, .app are bundles and cannot start directly from Terminal.
To Edit your .bash_profile:
Type in Terminal nano .bash_profile (make sure your are in your home-directory test it with the
pwd
command. Usually/Users/Username
.add the alias Line above at the end of the document.
- type CTRL-O to save the file
- type CTRL-X to exit nano
- type
source .bash_profile
to update - type safari to start Safari.
You can do this with most of the applications in the /Application-Folder.
This is a very special case - I would think open is the better command unless you have a very special need.
– Mark
9 hours ago
add a comment |
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
which
searches for binaries in the $PATH, a.k.a. command-line tools. User applications are not such tools and not available in the command line.
While Google Chrome.app is an application, the chrome
binary is not usually added to the $PATH because it is not a command line tool — if you just run chrome
in Terminal your shell will inform you that the command cannot be found.
To find the path to an application, you can use lsregister, which is a tool for adding and querying the Launch Services database, used by macOS in part to find applications. You can -dump
the database and filter with grep
.
/System/L*/Fr*/CoreSe*/V*/A/F*/L*/V*/A/S*/lsregister -dump |
grep -ie "path:.*safari"
path: /Applications/Safari.app
This will return every instance of Safari registered with Launch Services, which will include backups. If you just want to open Safari, you shouldn't be dealing with getting paths and handling it yourself; instead, get macOS to do that for you: open -a Safari
.
1
As much as I love the wildcards, I worry that someday Apple will add another service with a similar path and break the commands. It would be good to expand the path fully; it also makes it clearer just what’s being executed.
– nneonneo
3 hours ago
@nneonneo I was under the impression that first point wasn’t an issue, since providing the full name of the tool at the end will ensure the correct tool is always found, for example try running/System/*/*/*/*/A/*/*/*/A/*/lsregister
— the path given in the answer will be faster than the path in this comment since the answer provides enough to be unique, but both should work just as well! (‘A’ is preserved in this minimal path since ‘Current’ is symlinked to ‘A’.) I’ll see about grabbing the full path and adding it to the answer if you really think it improves clarity.
– grg♦
3 hours ago
I mean, I just don’t see how a bunch of wildcards is clear at all as to what’s being run. I would much rather see a long, deep path than a bunch of wildcards, and I think that would be a lot clearer.
– nneonneo
2 hours ago
the chrome binary is not usually added to the $PATH because it is not a command line tool
. Uh, well, considering it explicitly supportsheadless
mode, and I have several projects that uses it extensively from the CLI, I have to say I think you're incorrect.
– Fake Name
15 mins ago
add a comment |
which
searches for binaries in the $PATH, a.k.a. command-line tools. User applications are not such tools and not available in the command line.
While Google Chrome.app is an application, the chrome
binary is not usually added to the $PATH because it is not a command line tool — if you just run chrome
in Terminal your shell will inform you that the command cannot be found.
To find the path to an application, you can use lsregister, which is a tool for adding and querying the Launch Services database, used by macOS in part to find applications. You can -dump
the database and filter with grep
.
/System/L*/Fr*/CoreSe*/V*/A/F*/L*/V*/A/S*/lsregister -dump |
grep -ie "path:.*safari"
path: /Applications/Safari.app
This will return every instance of Safari registered with Launch Services, which will include backups. If you just want to open Safari, you shouldn't be dealing with getting paths and handling it yourself; instead, get macOS to do that for you: open -a Safari
.
1
As much as I love the wildcards, I worry that someday Apple will add another service with a similar path and break the commands. It would be good to expand the path fully; it also makes it clearer just what’s being executed.
– nneonneo
3 hours ago
@nneonneo I was under the impression that first point wasn’t an issue, since providing the full name of the tool at the end will ensure the correct tool is always found, for example try running/System/*/*/*/*/A/*/*/*/A/*/lsregister
— the path given in the answer will be faster than the path in this comment since the answer provides enough to be unique, but both should work just as well! (‘A’ is preserved in this minimal path since ‘Current’ is symlinked to ‘A’.) I’ll see about grabbing the full path and adding it to the answer if you really think it improves clarity.
– grg♦
3 hours ago
I mean, I just don’t see how a bunch of wildcards is clear at all as to what’s being run. I would much rather see a long, deep path than a bunch of wildcards, and I think that would be a lot clearer.
– nneonneo
2 hours ago
the chrome binary is not usually added to the $PATH because it is not a command line tool
. Uh, well, considering it explicitly supportsheadless
mode, and I have several projects that uses it extensively from the CLI, I have to say I think you're incorrect.
– Fake Name
15 mins ago
add a comment |
which
searches for binaries in the $PATH, a.k.a. command-line tools. User applications are not such tools and not available in the command line.
While Google Chrome.app is an application, the chrome
binary is not usually added to the $PATH because it is not a command line tool — if you just run chrome
in Terminal your shell will inform you that the command cannot be found.
To find the path to an application, you can use lsregister, which is a tool for adding and querying the Launch Services database, used by macOS in part to find applications. You can -dump
the database and filter with grep
.
/System/L*/Fr*/CoreSe*/V*/A/F*/L*/V*/A/S*/lsregister -dump |
grep -ie "path:.*safari"
path: /Applications/Safari.app
This will return every instance of Safari registered with Launch Services, which will include backups. If you just want to open Safari, you shouldn't be dealing with getting paths and handling it yourself; instead, get macOS to do that for you: open -a Safari
.
which
searches for binaries in the $PATH, a.k.a. command-line tools. User applications are not such tools and not available in the command line.
While Google Chrome.app is an application, the chrome
binary is not usually added to the $PATH because it is not a command line tool — if you just run chrome
in Terminal your shell will inform you that the command cannot be found.
To find the path to an application, you can use lsregister, which is a tool for adding and querying the Launch Services database, used by macOS in part to find applications. You can -dump
the database and filter with grep
.
/System/L*/Fr*/CoreSe*/V*/A/F*/L*/V*/A/S*/lsregister -dump |
grep -ie "path:.*safari"
path: /Applications/Safari.app
This will return every instance of Safari registered with Launch Services, which will include backups. If you just want to open Safari, you shouldn't be dealing with getting paths and handling it yourself; instead, get macOS to do that for you: open -a Safari
.
edited 10 hours ago
answered 12 hours ago
grg♦grg
138k25219323
138k25219323
1
As much as I love the wildcards, I worry that someday Apple will add another service with a similar path and break the commands. It would be good to expand the path fully; it also makes it clearer just what’s being executed.
– nneonneo
3 hours ago
@nneonneo I was under the impression that first point wasn’t an issue, since providing the full name of the tool at the end will ensure the correct tool is always found, for example try running/System/*/*/*/*/A/*/*/*/A/*/lsregister
— the path given in the answer will be faster than the path in this comment since the answer provides enough to be unique, but both should work just as well! (‘A’ is preserved in this minimal path since ‘Current’ is symlinked to ‘A’.) I’ll see about grabbing the full path and adding it to the answer if you really think it improves clarity.
– grg♦
3 hours ago
I mean, I just don’t see how a bunch of wildcards is clear at all as to what’s being run. I would much rather see a long, deep path than a bunch of wildcards, and I think that would be a lot clearer.
– nneonneo
2 hours ago
the chrome binary is not usually added to the $PATH because it is not a command line tool
. Uh, well, considering it explicitly supportsheadless
mode, and I have several projects that uses it extensively from the CLI, I have to say I think you're incorrect.
– Fake Name
15 mins ago
add a comment |
1
As much as I love the wildcards, I worry that someday Apple will add another service with a similar path and break the commands. It would be good to expand the path fully; it also makes it clearer just what’s being executed.
– nneonneo
3 hours ago
@nneonneo I was under the impression that first point wasn’t an issue, since providing the full name of the tool at the end will ensure the correct tool is always found, for example try running/System/*/*/*/*/A/*/*/*/A/*/lsregister
— the path given in the answer will be faster than the path in this comment since the answer provides enough to be unique, but both should work just as well! (‘A’ is preserved in this minimal path since ‘Current’ is symlinked to ‘A’.) I’ll see about grabbing the full path and adding it to the answer if you really think it improves clarity.
– grg♦
3 hours ago
I mean, I just don’t see how a bunch of wildcards is clear at all as to what’s being run. I would much rather see a long, deep path than a bunch of wildcards, and I think that would be a lot clearer.
– nneonneo
2 hours ago
the chrome binary is not usually added to the $PATH because it is not a command line tool
. Uh, well, considering it explicitly supportsheadless
mode, and I have several projects that uses it extensively from the CLI, I have to say I think you're incorrect.
– Fake Name
15 mins ago
1
1
As much as I love the wildcards, I worry that someday Apple will add another service with a similar path and break the commands. It would be good to expand the path fully; it also makes it clearer just what’s being executed.
– nneonneo
3 hours ago
As much as I love the wildcards, I worry that someday Apple will add another service with a similar path and break the commands. It would be good to expand the path fully; it also makes it clearer just what’s being executed.
– nneonneo
3 hours ago
@nneonneo I was under the impression that first point wasn’t an issue, since providing the full name of the tool at the end will ensure the correct tool is always found, for example try running
/System/*/*/*/*/A/*/*/*/A/*/lsregister
— the path given in the answer will be faster than the path in this comment since the answer provides enough to be unique, but both should work just as well! (‘A’ is preserved in this minimal path since ‘Current’ is symlinked to ‘A’.) I’ll see about grabbing the full path and adding it to the answer if you really think it improves clarity.– grg♦
3 hours ago
@nneonneo I was under the impression that first point wasn’t an issue, since providing the full name of the tool at the end will ensure the correct tool is always found, for example try running
/System/*/*/*/*/A/*/*/*/A/*/lsregister
— the path given in the answer will be faster than the path in this comment since the answer provides enough to be unique, but both should work just as well! (‘A’ is preserved in this minimal path since ‘Current’ is symlinked to ‘A’.) I’ll see about grabbing the full path and adding it to the answer if you really think it improves clarity.– grg♦
3 hours ago
I mean, I just don’t see how a bunch of wildcards is clear at all as to what’s being run. I would much rather see a long, deep path than a bunch of wildcards, and I think that would be a lot clearer.
– nneonneo
2 hours ago
I mean, I just don’t see how a bunch of wildcards is clear at all as to what’s being run. I would much rather see a long, deep path than a bunch of wildcards, and I think that would be a lot clearer.
– nneonneo
2 hours ago
the chrome binary is not usually added to the $PATH because it is not a command line tool
. Uh, well, considering it explicitly supports headless
mode, and I have several projects that uses it extensively from the CLI, I have to say I think you're incorrect.– Fake Name
15 mins ago
the chrome binary is not usually added to the $PATH because it is not a command line tool
. Uh, well, considering it explicitly supports headless
mode, and I have several projects that uses it extensively from the CLI, I have to say I think you're incorrect.– Fake Name
15 mins ago
add a comment |
This is working as designed.
which is a command line executable that looks on your path (and other parts of shell environment) to find things you can start from the command line
Applications like Safari (anything bundled as an application which will be a directory ending in .app with certain files in specific sub directories) are not launched from the command line. They are launched from the desktop and not via any shell commands.
You can however launch applications from the command line using the command open. man open gives details. The example to launch Safari is open -a Safari
Note that if you are trying to open Safari when you login putting this command in your shell files will not work as the shell is not run until you launch Terminal.app.
The easiest way to launch Safari at login is to run the app from the desktop, right click on the app's icon in the dock and choose Options then Open at Login.
There is also a list of things that are launched at login for each user in System Preferences->Users & Groups and this can be edited there.
add a comment |
This is working as designed.
which is a command line executable that looks on your path (and other parts of shell environment) to find things you can start from the command line
Applications like Safari (anything bundled as an application which will be a directory ending in .app with certain files in specific sub directories) are not launched from the command line. They are launched from the desktop and not via any shell commands.
You can however launch applications from the command line using the command open. man open gives details. The example to launch Safari is open -a Safari
Note that if you are trying to open Safari when you login putting this command in your shell files will not work as the shell is not run until you launch Terminal.app.
The easiest way to launch Safari at login is to run the app from the desktop, right click on the app's icon in the dock and choose Options then Open at Login.
There is also a list of things that are launched at login for each user in System Preferences->Users & Groups and this can be edited there.
add a comment |
This is working as designed.
which is a command line executable that looks on your path (and other parts of shell environment) to find things you can start from the command line
Applications like Safari (anything bundled as an application which will be a directory ending in .app with certain files in specific sub directories) are not launched from the command line. They are launched from the desktop and not via any shell commands.
You can however launch applications from the command line using the command open. man open gives details. The example to launch Safari is open -a Safari
Note that if you are trying to open Safari when you login putting this command in your shell files will not work as the shell is not run until you launch Terminal.app.
The easiest way to launch Safari at login is to run the app from the desktop, right click on the app's icon in the dock and choose Options then Open at Login.
There is also a list of things that are launched at login for each user in System Preferences->Users & Groups and this can be edited there.
This is working as designed.
which is a command line executable that looks on your path (and other parts of shell environment) to find things you can start from the command line
Applications like Safari (anything bundled as an application which will be a directory ending in .app with certain files in specific sub directories) are not launched from the command line. They are launched from the desktop and not via any shell commands.
You can however launch applications from the command line using the command open. man open gives details. The example to launch Safari is open -a Safari
Note that if you are trying to open Safari when you login putting this command in your shell files will not work as the shell is not run until you launch Terminal.app.
The easiest way to launch Safari at login is to run the app from the desktop, right click on the app's icon in the dock and choose Options then Open at Login.
There is also a list of things that are launched at login for each user in System Preferences->Users & Groups and this can be edited there.
answered 12 hours ago
MarkMark
20.2k115795
20.2k115795
add a comment |
add a comment |
On macOS applications aren‘t part of the standard PATH and can‘t be started by calling them from the command line (well, yes, they can, but it‘s not so easy). But you can use
open foo.html
or
open -a Safari
to start Safari from bash.
add a comment |
On macOS applications aren‘t part of the standard PATH and can‘t be started by calling them from the command line (well, yes, they can, but it‘s not so easy). But you can use
open foo.html
or
open -a Safari
to start Safari from bash.
add a comment |
On macOS applications aren‘t part of the standard PATH and can‘t be started by calling them from the command line (well, yes, they can, but it‘s not so easy). But you can use
open foo.html
or
open -a Safari
to start Safari from bash.
On macOS applications aren‘t part of the standard PATH and can‘t be started by calling them from the command line (well, yes, they can, but it‘s not so easy). But you can use
open foo.html
or
open -a Safari
to start Safari from bash.
answered 12 hours ago
nohillside♦nohillside
53.3k14112157
53.3k14112157
add a comment |
add a comment |
Add following in your .bash_profile.
alias safari="/Applications/Safari.app/Contents/MacOS/Safari"
You can now start safari in your Terminal. As mentioned before, .app are bundles and cannot start directly from Terminal.
To Edit your .bash_profile:
Type in Terminal nano .bash_profile (make sure your are in your home-directory test it with the
pwd
command. Usually/Users/Username
.add the alias Line above at the end of the document.
- type CTRL-O to save the file
- type CTRL-X to exit nano
- type
source .bash_profile
to update - type safari to start Safari.
You can do this with most of the applications in the /Application-Folder.
This is a very special case - I would think open is the better command unless you have a very special need.
– Mark
9 hours ago
add a comment |
Add following in your .bash_profile.
alias safari="/Applications/Safari.app/Contents/MacOS/Safari"
You can now start safari in your Terminal. As mentioned before, .app are bundles and cannot start directly from Terminal.
To Edit your .bash_profile:
Type in Terminal nano .bash_profile (make sure your are in your home-directory test it with the
pwd
command. Usually/Users/Username
.add the alias Line above at the end of the document.
- type CTRL-O to save the file
- type CTRL-X to exit nano
- type
source .bash_profile
to update - type safari to start Safari.
You can do this with most of the applications in the /Application-Folder.
This is a very special case - I would think open is the better command unless you have a very special need.
– Mark
9 hours ago
add a comment |
Add following in your .bash_profile.
alias safari="/Applications/Safari.app/Contents/MacOS/Safari"
You can now start safari in your Terminal. As mentioned before, .app are bundles and cannot start directly from Terminal.
To Edit your .bash_profile:
Type in Terminal nano .bash_profile (make sure your are in your home-directory test it with the
pwd
command. Usually/Users/Username
.add the alias Line above at the end of the document.
- type CTRL-O to save the file
- type CTRL-X to exit nano
- type
source .bash_profile
to update - type safari to start Safari.
You can do this with most of the applications in the /Application-Folder.
Add following in your .bash_profile.
alias safari="/Applications/Safari.app/Contents/MacOS/Safari"
You can now start safari in your Terminal. As mentioned before, .app are bundles and cannot start directly from Terminal.
To Edit your .bash_profile:
Type in Terminal nano .bash_profile (make sure your are in your home-directory test it with the
pwd
command. Usually/Users/Username
.add the alias Line above at the end of the document.
- type CTRL-O to save the file
- type CTRL-X to exit nano
- type
source .bash_profile
to update - type safari to start Safari.
You can do this with most of the applications in the /Application-Folder.
answered 12 hours ago
dante12dante12
1,254512
1,254512
This is a very special case - I would think open is the better command unless you have a very special need.
– Mark
9 hours ago
add a comment |
This is a very special case - I would think open is the better command unless you have a very special need.
– Mark
9 hours ago
This is a very special case - I would think open is the better command unless you have a very special need.
– Mark
9 hours ago
This is a very special case - I would think open is the better command unless you have a very special need.
– Mark
9 hours ago
add a comment |