defaults write com.barebones.textwrangler Misc:SkipSCMAdminDirsWhenScanningFolders -bool NO

Note that this behavior represents a change from previous versions, in which you could search inside of such directories by using "Search Invisible Folders".

defaults write com.barebones.textwrangler Clipboard:ConvertNonBreakingSpacesWhenPasting -bool NO

x{d}
x{0d}
x{00d}
x{000d}

match_string (text) : for Grep search results, contains the text matched by the pattern

Usage: twfind <options> <string> <path ...>

-h, --help print this help and exit -v, --version print detailed version information and exit -V, --short-version print abbreviated version information and exit -n, --case-sensitive search case sensitive (default: case insensitive) -g, --grep interprets "<string>" as a regular expression -w, --match-words only return matches that fall on word boundaries -R, --no-nested-folders suppress searching of nested folders -I, --search-invisible-folders search invisible folders --all-file-types search all file types (default: text files only) --name-pattern only search files whose names match the given pattern (may be used multiple times) --gui open a results window instead of returning results -c, --count only print number of matches found -Z, --null separate results lines with NUL instead of newline -S, --suppress-context only print file path and line number of match -E, --editor-commands print results in the form ofeditcommands -0 interpret input separated with NUL instead of newline

You can combine single-character switches. Thus,

twfind -ngw some-string ...

is equivalent to

twfind -n -g -w some-string ...

You can also use "--" to end the parsing of switches, in cases where you need to specify a search string or file path that begins with two hyphens:

twfind some-string -- --name-of-some-file

It is possible to search more than one folder at a time by specifying multiple "path" arguments. Apart from the special case of using "--", the first non-hyphenated argument is interpreted as the search string (or pattern, if -g is specified) and all others are file paths. So, you could write:

twfind error /var/log /Library/Logs/

and this will cause twfind to search for the string "error" in two different folders.

If no search paths are specified on the command line, twfind will attempt to read them from standard input. This makes it an attractive target for the output of other tools such as find. For example:

find . -name "*.py" -print | twfind blah

takes the paths printed by find and searches those files.

The input is expected to be separated by Unix newlines (n). In cases where standard input is generated programmatically and the paths are separated with a NUL, you can pass a -0 on the command line. Again using find as an example input source:

find . -name "*.py" -print0 | twfind blah -0

A --name-pattern option is available for filtering files by name in the directory(ies) being searched. The wildcard syntax is the same as that used by the "Matches Wildcard" file filter term:

'?' matches any single character;
'#' matches any digit;
'*' matches any run of characters;
'' is used to escape the next character (for matching literal '?', '#', or '*')

so, twfind foo . --name-pattern "*.py" will search for the string foo in the current working directory, in every file whose name ends in .py.

Ordinarily, twfind returns results in this form:

/path/to/file:NN <line>

where "NN" is the line number containing the match, and "<line>" is the text of the line where the match occurred. You can modify the output in a few different was: -S will suppress the line, which is a prerequisite if you want to use the output of twfind as input to another tool (like xargs).

If you like, you can have twfind generate output in the form of edit commands, each of which can be executed to open the file and select the line. Use -E. (Note that that this implies -S and will suppress the context.)

Whether or not you use -S, the -Z switch modifies the output by using a NUL (ASCII 0) character to separate the lines of output, rather than a newline (ASCII 10). This can be useful for programmatically parsing the output, or running it through xargs -0.

Using -c will suppress all of the output, and simply return the total number of matches that were found.

It's also possible to use twfind as a front end for the GUI multi-file search. Add --gui to the command line, and the search will start and present a Search Results window, rather than returning any text results to the tool. (This option causes the tool to exit as soon as the search is started.)

Note also that using -h, -V, or -v will cause the tool to exit immediately without performing a search, even if there are valid search string and options provided.

BB_DOC_LANGUAGE Name of the document's current language (not set if language is "none") BB_DOC_MODE Emacs mode of the document's current language BB_DOC_NAME name of the document BB_DOC_PATH path of the document (not set if doc is unsaved) BB_DOC_SELEND (zero-based) end of the selection range (not set if not text document) BB_DOC_SELEND_COLUMN (one-based) de-tabbed column number of BB_DOC_SELEND BB_DOC_SELEND_LINE (one-based) line number of BB_DOC_SELEND BB_DOC_SELSTART (zero-based) start of the selection range (not set if not text document) BB_DOC_SELSTART_COLUMN (one-based) de-tabbed column number of BB_DOC_SELSTART BB_DOC_SELSTART_LINE (one-based) line number of BB_DOC_SELSTART

NB: selection ranges and other offsets are expressed in characters, not bytes.

# pay attention to changes in RCS keywords when comparing files defaults write com.barebones.textwrangler Diff:IgnoreRCSKeywords -bool NO

The warning includes an option to compare the open document against what's on disk, in cases where you are saving a text document.

This is the native type provided by Cocoa applications. By using it in preference to the UTF-16 variants we avoid getting a translated version of the rich text data which is also on the pasteboard. In certain situations, this can result in data which differs by more than just the encoding. (For example, when copying from Safari, WebKit places non-breaking space translated plain-text on the pasteboard, and tab-delimited data for any selected tables. But the translation of the rich text data results in something quite different.)

tell application "TextWrangler" to close text document 1 saving yes saving in file "Boom Box:Users:siegel:Desktop:text.txt"