Sarah, Did you get it to work? Note there are two special characters in the command, these are important to get right...
1. There is a "pipe" or "OR bar" as some might call it, (In US keyboards it is a shifted back slash). This was between say and open. This command is used in terminal to say send all the output from the left side into the right side. (I hope that simplification makes sense. 2. A minus sign in front of the f. the minus sign makes the f an option instead of a file name argument. HTH Best wishes, Jon On 24/09/2010, Sarah Alawami <marri...@gmail.com> wrote: > I think I got it but not sure. it opened something but my text edit window > was blank. I'll look again when I get home. > > S > On Sep 24, 2010, at 12:09 PM, Jonathan Cohn wrote: > >> It is more likely that I didn't write the command correcI will test my >> command with a cut and paste from home to ensure Iformatted it >> correctly. It should'nt take more then 3 seconds. >> >> Jon >> instantaenious. >> >> On 23/09/2010, Sarah Alawami <marri...@gmail.com> wrote: >>> Hmm how long does this process of manual creation last? I waited about 1 >>> to >>> 2 minutes and text edit did not open with the manual for the say command. >>> >>> Take care. Maybe I'm not patient enough. >>> >>> S >>> On Sep 23, 2010, at 6:37 PM, Jonathan C. Cohn wrote: >>> >>>> I was playing around with making fun of "droid" adds. So I created a >>>> sound >>>> file... >>>> >>>> say -o droiddead.aiff -v cello "droid. is. dead. Long live I Phone" >>>> >>>> I thought hmm, I should be able to open this from the termial and not >>>> have to switch to the finder. >>>> >>>> In the process, I discoverd that there is a -f option to open that we >>>> will >>>> find useful. >>>> >>>> An example but not too usefull. >>>> >>>> man say | open -f >>>> >>>> This command will create a manual for the "say" command and then open >>>> that >>>> manual in textedit (or perhaps your preferred text editor ). >>>> >>>> Have fun with this, >>>> >>>> Jon >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups >>>> "MacVisionaries" group. >>>> To post to this group, send email to macvisionar...@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 macvisionar...@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 macvisionar...@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 macvisionar...@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 macvisionar...@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.
