On Wed, Apr 30, 2014 at 3:07 PM, Ken G. Brown wrote:
> Shouldn’t the install process ensure the utility is in working state or
> does a person always have to quit terminal and restart, or perhaps open a
> new Terminal window?
It is not sanely possible for programs to inject PATH changes or comm
I did realized that tree was a command line utility, that was why I wanted it.
After installing it, tree was still not working from command line. At some
later time, it magically started working.
Perhaps I had quit Terminal and restarted at some point, I don’t recall.
Shouldn’t the install proce
On Wed, Apr 23, 2014 at 1:27 PM, Ken G. Brown wrote:
>
> Now that tree apparently is installed, how do I run it, where is the
> executable?
The executable is probably installed at /opt/local/bin/tree
You can check for sure using "port contents tree"
> Is there something I am missing in setting
I’ve just installed the tree utility using Pallet.app gui for MacPorts.
I had tried earlier with Port Authority but had a few crashes.
What is the best gui for MacPorts?
Now that tree apparently is installed, how do I run it, where is the executable?
Is there something I am missing in setting
