Re: About the terminal...
A second way is to make a symbolic link to the file in your usr/bin subdirectory.
Type ln -s [pathname of F@H binary] /usr/bin/[link name]
You can then type in the linkname anywhere in your terminal session and it will have the same effect as typing the pathname.
That's because there's no default file extension. Appending .command to any file forces it to be opened with terminal, whether it is executable or not. So provided the binary has been made executable, (w/chmod +x) you can have it open w/terminal by default using this method. You can take this a step further and have it automatically run at login using the login control panel and adding the .commad file. This will luanch the binary through terminal automatically.Originally posted by dnte42
First, is there any easy way to script the terminal to open the file or to launch it on startup? OS X just treats it as an unknown document.
A second way is to make a symbolic link to the file in your usr/bin subdirectory.
Type ln -s [pathname of F@H binary] /usr/bin/[link name]
You can then type in the linkname anywhere in your terminal session and it will have the same effect as typing the pathname.
Not that I have seen. My solution is to create an alias to the logfile in the work directory and open that when I care to know how far I've gone. I know of no way in F@H 3 to display the frames in the terminal.Second, is there any way to get the terminal to give status updates (i.e. the frames finished as in the logs)? Thanks.