I've seen Regex handle finding and replacing backreferences in different ways, but I can't figure out how it works in Textastic for Mac and there isn't any documentation that I can find. Below is a discussion from a Regex tutorial website. None of the methods discussed seem to work for me.

> Numbered Backreferences

> If your regular expression has named or numbered capturing groups, then you can reinsert the text matched by any of those capturing groups in the replacement text. Your replacement text can reference as many groups as you like, and can even reference the same group more than once. This makes it possible to rearrange the text matched by a regular expression in many different ways. As a simple example, the regex \*(\w+)\* matches a single word between asterisks, storing the word in the first (and only) capturing group. The replacement text <b>\1</b> replaces each regex match with the text stored by the capturing group between bold tags. Effectively, this search-and-replace replaces the asterisks with bold tags, leaving the word between the asterisks in place. This technique using backreferences is important to understand. Replacing *word* as a whole with <b>word</b> is far easier and far more efficient than trying to come up with a way to correctly replace the asterisks separately.

> The \1 syntax for backreferences in the replacement text is borrowed from the syntax for backreferences in the regular expression. \1 through \9 are supported by the JGsoft applications, Delphi, Perl (though deprecated),Python, Ruby, PHP, R, and Tcl. Double-digit backreferences \10 through \99 are supported by the JGsoft applications, Delphi, and Python. If there are not enough capturing groups in the regex for the double-digit backreference to be valid, then all these flavors treat \10 through \99 as a single-digit backreference followed by a literal digit. The flavors that support single-digit backreferences but not double-digit backreferences also do this.

> $1 through $99 for single-digit and double-digit backreferences are supported by the JGsoft applications, Delphi,.NET, Java, JavaScript, VBScript, PCRE2, PHP, and XPath. These are also the variables that hold text matched by capturing groups in Perl. If there are not enough capturing groups in the regex for a double-digit backreference to be valid, then $10 through $99 are treated as a single-digit backreference followed by a literal digit by all these flavors except .NET, Perl, and PCRE2.

>Putting curly braces around the digit ${1} isolates the digit from any literal digits that follow. This works in the JGsoft applications, Delphi, .NET, Perl, PCRE2, PHP, and XRegExp.

http://www.regular-expressions.info/replacebackref.html

The ability to open large files (files larger than the amount of available RAM) would be a very useful feature. Currently, Textastic seems to load the entire file into memory. This is fine until you want to view a 10 GB text file on Mac with 4 GB of RAM.

Large file support can be implemented using file memory-mapping, where only a portion of the file being viewed is loaded into memory:

- https://en.wikipedia.org/wiki/Memory-mapped_file

Why would anyone want to view such large files? Anyone working with server log files. Run-away logs, or logs from high-volume servers can easily reach multiple gigabytes in size.

The only text editor that I know of that is able to open files larger than the available amount of memory is EditPad Pro, a Windows only editor. You can open a 10 GB text file in EditPad Pro, and it appears instantly in the editor, because only the part of the file being viewed is loaded. I miss EditPad Pro on the Mac, but I don't want to install a 20 GB Windows virtual machine just to open large files quickly on my Mac.

If Textastic supported large files, it would be a real differentiator from all the other text editors out there, and I think it would be especially useful on iOS, where the amount of available memory is relatively small. I hope that large file support will be considered for a future version of Textastic. If not, that's okay. Very few text editors have it anyway.  (-:

I have to use CMD + LEFT/RIGHT/UP/DOWN for fast navigation. On full size keyboards the quick navigation (HOME/END + PG UP/DOWN) keys are unused. Any other editor (e.g. MacVIM) offers these keys functional.

Is it possible to show the full POSIX path in the window title. This makes it easier to identify files when multiple tabs are open, especially when they have the same name.
I am aware that the information is available by right-clicking on the file name, but this is fiddly when quickly switching through many different tabs.