> In addition, there is no harm in using ./something in lieu of just > something. In fact, there are cases where you HAVE TO use the > ./something form because the plain something will not work. I find it > is simpler to always use ./ to avoid these cases.
Herb and Robert, I really appreciate your replies.. because it answered some questions I had while I am learning some more of the command line these days.. (just as I need something.. to further stumble my way through to the next step in what I am *really* trying to do ;-) I really want to ask more questions here .. but perhaps BBedit users will (rightly) feel I am going too OT. (Like WHY does it not work to just be in the right directory and type the name of a command?; why does the command have to have the './' first? I guess I need to find a good CL forum and ask about what you meant Herb, when you referred to "PATH"? Thanks -Govinda -- You received this message because you are subscribed to the "BBEdit Talk" discussion group on Google Groups. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at <http://groups.google.com/group/bbedit?hl=en> If you have a feature request or would like to report a problem, please email "[email protected]" rather than posting to the group. Follow @bbedit on Twitter: <http://www.twitter.com/bbedit>
