The app shuts down when I try to connect to my SharePoint WebDAV server. Seems like a great editor but I can't use it.

Some keys on the sliding row get used more than others. It would be good to be able to adjust the sequence. For example i use (){} and ; a lot!

I've found that I'm missing the TextExpander and Additional Keys panel when entering text in the Find and Replace text boxes.

Any reason they're not active in that UI?
Is that easy to add?

Currently, Textastic interprets FTP file listings as UTF-8.

A user reported that this doesn't work for an FTP server which uses Korean (EUC_KR) character encoding. In this case, Textastic shows an empty file listing when there is at least one file with Korean characters in the directory.

There should be a way to choose the character encoding for each FTP connection.

Can you add a button bar for frequenly used text? User assignable and/or script type specific buttons with common code blocks that would paste to the cursor position?

Why can't I preview my html

In PHP, when you use // for commenting out lines instead of /*, instead of one single line ALL lines are colored gray.. // is used to comment out just one single line in PHP and is often used.. With your app, all lines after // are turned gray, as if it would function the same as /* So, since I start all my files with: //Note:... my entire files are grayed out.. ......Thanks! Great app you're creating here, keep it up! :)

The other day I tried sending a UTF-8 encoded LaTeX file as an attachment, only to find out that when the file arrived, non-ASCII characters (such as German ö, ä, ü and ß) had been replaced by two question marks.

I'm loving Textastic - really handy for editing files locally on my morning commute (with terrible reception) and then upload them on a decent 4G connection at the end.

I've just had one annoyance so far which is that detection of file type appears to go by the file extension only. The problem is that I commonly omit the extension for executable scripts (e.g. Python) so that the language is an implementation detail that can be changed later without needing to change anything that calls them.

It would be great if extensionless files could be detected based on Shebang line. So, if the first line of the file starts with #! and something like "python" or "ruby" occurs after it then the appropriate mode can be chosen. I suggest a loose parsing strategy like that to cope with different paths to interpreters, use of the "env" utility, etc.