Script define what it uses for input and does with the output, so youĬan say "take either the current selection or the current document, pass ![]() Pretty broad range of environment variables for scripts, and lets each Scripts create dialogs for user interaction. Well, there are some clever ways around that, which are the "fewĮxceptions" I was thinking about - TextMate has a library that lets its > input and environment variables to a shell script and getting standard > TextMate’s bundles are-with few exceptions-limited to passing standard > with, from bash to Ruby.¹ The flip side of that, though, is that > "TextMate lets you write in any language you can script a Unix shell > According to the article that started this discussion, the same 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.Īt least that's the way I've always seen it… I've always considered scripts, grep patterns, and text factories to be quick, throw away utilities to complete a specific task.Ĭlippings sets and language modules take a long time to develop, and have long-term value. usr/local/bin/uncrustify -c ~/.uncrustify.objc -l OC -q -f "$1"ĭoes the world need to see before the pattern is obvious? I've got other scripts that run various unix tools, and slam the document with the result. But while I was doing that work, it was invaluable. In fact, I don't need it any more, either. Do you need a script to convert a block of code from using an XTException class to a different Exception? Probably not. ![]() Looking through my own scripts, there's nothing that strikes me as useful to anyone else, because they manipulate specific data into specific forms. > for people who would love to use some of these features but just don't > hours and hours of wheel-reinventing, is that they'd provide examples The great thing about sharing these, apart from saving > Clippings and Language Modules don't seem to get updated with any > Filters, AppleScripts, Text Factories or Grep Patterns. > Module Library, but there are no user-contributed Unix Scripts, Unix Bare Bones hosts a BBEdit Clippings Library and a Language > I'd love to see more organized sharing of BBEdit scripts etc. Repository for BBEdit to encourage sharing and learning about this stuff. Perhaps there should be a community-driven scripts That you just kind of have to know about, or ask the right people for, Impression from this list that there's a *lot* more scripts out there ![]() Publicly-available scripts for BBEdit are, well, pretty old I get the Project somebody else would have to take up. However, I doubt I'm alone in findingĪppleScript to be a *remarkably* impenetrable language - this is a Unlike a few of the other editors that have popped up recently, youĬan't convert them directly, but I suspect a lot of them could be What I'd like to see is a guide for porting TextMate bundles to BBEdit. Lack of "smart" indenting - that is, syntax-aware - is somewhere in Language Modules to reference one another is a stumbling block, and the (No automatic typing pairs is a nitpick, the inability for Codeless Those are nitpicks, although a couple are real stumbling blocks for me. Still some differences in both implementation and philosophy. I don't think migrating is that difficult these days, although there are That's actually my article - Marco reblogged it. > a brief look around for articles about migrating to BBEdit from TextMate. In response to Marco's article "Text Editor Intervention", I had
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |