The specific app is only stored on my admin account (which I am using) under /user/applications. When I input that string it gives me a message saying "No such file or directory".
One day you'll come back here to read that post and chuckle... because there's so much 'wrong' in there, it's hard to know where to begin. Fortunately, others have pointed out that "/user/applications" is one
highly unlikely path... so Terminal's response (no such file or directory) is most certainly right on the money. Along with the drag-n-drop method suggested by Ganesha, we can also use copy/paste (from Finder to Terminal) in much the same way.
A third technique to obtain the proper path is by using
tab-completion.
E.g.,
cd /u<tab>/j<tab>/a<tab>/c<tab>/c<tab>
Depending on the existence of such items, the (auto-formatted) result on the command line might end up looking something like this:
cd /Users/jwalker/Applications/Carbon\ Copy\ Cloner.app/Contents
The idea is to let
Readline do the heavy lifting: it sees what filesystem objects (or commands) actually exist, it fills out a possible pathname
each time tab is pressed, and it handles the formatting of all oddball characters in the name (not just spaces, but single quotes, slashes and other punctuation, whatever).
For better efficiency, we sometimes need to type more than one letter before hitting the tab key. And sometimes we'll need to hit tab two or three (or more) times in a row before we match the item we're after. Regardless, it's a huge timesaver.
FWIW, I use the following Readline bindings (which get sourced from my ~/.bashrc file):
bind '"\t": menu-complete'
bind '"\e\t": complete-command'
bind 'set completion-ignore-case on'
bind 'set mark-directories off'
bind 'set show-all-if-ambiguous on'
[those can also be entered right on the command line, so you can try before you buy.]
I repaired the permissions for the disk using the disk utility but its still not working.
Repairing permissions does absolutely
nothing inside anyone's *
home* folder. EDIT: pluswhich —if permissions were the problem, then —the message from Terminal would have been "Permission denied". When the error comes back as "No such file or directory", the problem is typically exactly that. [wrong pathname, or right pathname to an item that's missing.]
I also tried it on another mac in my department and had the same problem
Expected.
PS: learn how to master the
ls (list) command, so you can see what's what (and where). E.g., if
cd claims some file or directory doesn't exist... then use
ls to
see what
does exist. Mistakes such as these (blindly entering a path) with the
rm command are often far less amusing.
