Wasn't saying it was off topic. Was saying that fully explaining
everything you can do in the shell would be just a huge document that
already exists in various forms out on the web. No need to reiterate it
here. Obviously if there are more specific questions we can try to help
but it would be like someone asking how to use a Mac. Just too broad a
topic to give proper treatment in an email.
CB
On 12/2/11 4:43 PM, Sean Murphy wrote:
Hi Chris,
Why is talking about the CLI off topic since the MAC is based upon
Unix and is the core of the OS.
Sean
----- Original Message ----- From: "Chris Blouch" <cblo...@aol.com>
To: <macvisionaries@googlegroups.com>
Sent: Friday, December 02, 2011 8:00 AM
Subject: Re: where to start i I want to automate terminal commands
In your utilities folder is a program called terminal which lets you
type commands in what is usually called a 'unix shell'. If you've used
DOS or Unix it will be quite familiar. So everything I described is done
inside of terminal. You can do things like copy a file by typing
cp original_file copy_file
where original_file is the name of the original file and copy_file is
what you want the copy named. You can also use the ls command to list
the contents of the current directory, or mv to move instead of copy a
file. The terminal/shell is a very powerful tool and it is beyond the
scope of this mailing list to tell you everything about it. Google
around for some tutorials on unix and bash. bash stands for Bourne Again
Shell and that is also created by Brian Fox of the GNU Project.
CB
On 12/1/11 3:10 PM, Ioana Gandrabur wrote:
Hi,
Thanks for the tips. I am afraid I don't know about shell and chmod.
Sorry for being so clueless. Any pointers are as usually very
appreciated.
Take care,
Ioana
On Nov 30, 2011, at 10:03 AM, Chris Blouch wrote:
You could just do the script in the shell as well and skip
automater. Just put each command line by line in a text file and
then modify the text file to be executable with
chmod a+x
after that you can just run that text file and it will execute all
the commands inside as though you had typed them. I often use this
for repetitive tasks and just name the file "g" for "Go". One tricky
bit is the shell will look in certain places (directory paths) for
files to run and often times this is not your present directory. So
unless I add the present directory (usually denoted as a dot or
period) to my path I have to specify it when doing my "g" command:
./g
If you want I can give you the commands to add . to your path and
avoid the ./ nonsense.
CB
On 11/29/11 8:52 PM, Ioana Gandrabur wrote:
Hi all,
I would love to create a script or what ever that I can call up to
perform a series of terminal commands. I had a look at the
automator and found a record option to type in all the steps. I
performed the actions but when I tried to run the action got an
error. I suspect that the key sequence goes to fast since it is
saying that terminal is not running when it was expected to.
Any ideas how to do this or where to look for prewritten scripts I
can modify?
Is the script editor a better option than automator?
I have no formal scripting experience but have read and written
jaws scripts using their manual but really nothing fancy.
Thanks for any suggestions.
Ioana
--
You received this message because you are subscribed to the Google
Groups "MacVisionaries" group.
To post to this group, send email to macvisionaries@googlegroups.com.
To unsubscribe from this group, send email to
macvisionaries+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/macvisionaries?hl=en.
--
You received this message because you are subscribed to the Google Groups
"MacVisionaries" group.
To post to this group, send email to macvisionaries@googlegroups.com.
To unsubscribe from this group, send email to
macvisionaries+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/macvisionaries?hl=en.
