christianiop.blogg.se

Bbedit 11.5 code#

Honorable mentions: Code Runner 2, Textastic. I still use BBEdit for one-off text editing functions it handles better like version diff. I’ve used (and owned) BBedit for decades, but Textmate is now my default shell script editor. Now Textmate handles that function for me as well. BBEdit was always a little clunky to me for running scripts and I used Code Runner too for prototyping. I actually like Textmate’s implementation a little better. Like BBEdit, it supports running scripts (Textmate also supports running selected lines) in the editor. In addition to great built-in support for shell editing, Textmate is also highly customizable (like BBEdit) and has good community support for sharing bundles. I was even able to easily add pragma mark support. It solved my code folding issues and provides function jump navigation. While all of them had something they did well, Textmate (currently 2.0rc4) is far and away the best one I’ve found. I spent some time checking out several other text editors looking for better shell script editing support. Here’s copy of the plist embedded in a Word doc file… I can’t include. This is really what I wanted, and finally achieved. If your long string contains too many (how many?) characters the color coding encounters a stack overflow and stops recognizing strings. Not ending a string at a newline character The long bash string looks something like this: I ran into this trying to get my script’s help text identified as a string. If you want to use a different string, then you’ll have to edit the CLM ist.īBEdit does have a bothersome limitation in color coding long (multi-line) strings. I used the string “EOC” to stand for End Of Comment. For my CLM a block quote must look like this: I discovered a neat way to create block quotes while developing my CLM posted by sunny256 on ( Block Comments in a Shell Script – Stack Overflow) There are probably similar ways invented by equally talented coders, but this is the first that popped up.

And BEST OF ALL, code folding and inclusion in the navigation menu of your script’s functions.

Color coding strings in double or single quotes.

Color code comments including block comments (what? how do you do a block comment in bash? - read on).

I did create a Codeless Language Module (CLM) which can be dropped into ~/Library/Application Support/Language Modules/ and will do the following for your bash scripts. But what I didn’t realize is that it doesn’t just use grep, but PCRE, which has some really powerful additions to grep.Īt any rate, I won’t bore you with the details. The first thing I had to learn was the extra power, and complexity, of PCRE (Perl Compatible Regular Expressions.) Power users of BBEdit already know that the find and replace function can use grep. The unix shell scripts language module does an OK job of coloring certain things like comments, strings and keywords, but it doesn’t recognize functions and therefore doesn’t offer code-folding or listing of your functions in the Navigation bar. It does have one small limitation that I was hoping version 11 would address and that is handling bash scripts better than just “unix shell scripts”. Now at version 11 it still doesn’t suck and in fact is still insanely great. BBEdit has been one of my favorite applications since I begin using it in the early nineties, or was it the late 80’s? At any rate, it just keeps getting better and if you do any kind of serious text editing on the Mac, be it HTML, CSS, Java, etc you really should be using BBEdit.