>> I'd love to see more organized sharing of BBEdit scripts etc.
> 
> Me too. Bare Bones hosts a BBEdit Clippings Library and a Language
> Module Library, but there are no user-contributed Unix Scripts, Unix
> Filters, AppleScripts, Text Factories or Grep Patterns. Even the
> Clippings and Language Modules don't seem to get updated with any
> regularity. The great thing about sharing these, apart from saving
> hours and hours of wheel-reinventing, is that they'd provide examples
> for people who would love to use some of these features but just don't
> have a clue how to go about it. (I'd think that might increase user
> satisfaction, but what do I know?)

Looking through my own scripts, there's nothing that strikes me as useful to 
anyone else, because they manipulate specific data into specific forms. Do you 
need a script to convert a block of code from using an XTException class to a 
different Exception? Probably not. In fact, I don't need it any more, either. 
But while I was doing that work, it was invaluable.

I've got other scripts that run various unix tools, and slam the document with 
the result. But how many examples of:

#!/bin/sh
/usr/local/bin/uncrustify -c ~/.uncrustify.objc -l OC -q -f "$1"

does the world need to see before the pattern is obvious?

I've always considered scripts, grep patterns, and text factories to be quick, 
throw away utilities to complete a specific task.

Clippings sets and language modules take a long time to develop, and have 
long-term value. Lots of people write php, or program in Erlang, so a php 
clipping set or Erlang language module serves a purpose beyond getting one job 
done.

At least that's the way I've always seen it…

Steve

-- 
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 bbedit@googlegroups.com
To unsubscribe from this group, send email to
bbedit+unsubscr...@googlegroups.com
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 "supp...@barebones.com" rather than posting to the group.
Follow @bbedit on Twitter: <http://www.twitter.com/bbedit>

Reply via email to