On Sunday, May 11, 2003, at 09:10 AM, John Delacour wrote: > At 8:45 am -0700 11/5/03, Bruce Van Allen wrote: >> Very nice, John. >> >> I made a slight change to have the script open the path list in >> BBEdit (I have the BBEdit tool installed, so I can call it with >> 'bbedit file' in Terminal.app). My next step will be to have Perl >> turn that path list over to my end-of-line converter... > That's not necessary, you can have the script itself do all that and > never need to see BBEdit at all. If all you want is a droplet that > converts line-endings in files dropped on it then that's a piece of > cake. Yes. I was just fiddling with your example, just to have the path file opened in BBEdit instead of TextEdit. My eol conversion utility has a rich set of options, batch converts files with any system's line-ending to duplicate files with line-endings of any other system, reports errors, and logs what it does. I usually evoke it with a BBEdit shell worksheet or run it from the command line; adding a droppable evocation that knows where it is would be handy. > What would be more interesting is an AS droplet that would act as > DropScript does, creating a new droplet with the perl routine loaded, > with the added features that it can stay open and that it knows where > it is. That doesn't sound too difficult. I haven't really the time, > but I'll see what I can come up within the next hour or two. Cool. - Bruce __bruce__van_allen__santa_cruz__ca__Thread Previous | Thread Next