Your comments

Those keys work for me as expected on OS X. Please note that the behavior on the Mac is different than on Windows. This is described in this Wikipedia article: http://en.wikipedia.org/wiki/Home_key (emphasis mine)

On most Mac OS X applications, the key works like the original on UNIX in the days of dumb-terminals, where Home moves to the start of a document. When the key is pressed, the window scrolls to the top, while the caret position does not change at all; that is, the Home key is tied to the current window, not the text box being edited. On Apple keyboards that do not have a Home key, one can press fn+ for the Home key functionality described above. To get the same result as the Windows platform (that is, going to the beginning of the current line of text), one can press Command+.
Thanks. This seems to be a bug in the TextMate syntax definition that is used by Textastic. The same happens in TextMate 1 and 2 on the Mac.

It seems to be related to the "_arg[i]->dotID()" call. As soon as I remove the "->" part, the syntax highlighting is correct.
Hello,

the default AppleScript .scpt files are binary files. You need to save the script as an .applescript file (file format: text) using the AppleScript editor on a Mac. Then you can edit it with syntax highlighting in Textastic.

Best regards,

Alexander Blach
Do you have a screenshot? I cannot reproduce the problem.
You can create new folders using the "+" button in the bottom toolbar.
Yes, I plan to add support for the document picker and iCloud Drive.
iOS 8 still has some keyboard bugs - especially when using the split keyboard on iPad.

Another user reported a workaround:

1. Merge the keyboard and put it back at the bottom.
2. Kill Textastic from the task switcher.
3. Restart Textastic.

Please let me know if that helps.