Your comments
Can you please send me the HTML file so I can try it on my own device?
If you add "<?php" in a fenced code block, you also need to add "?>" to finish the php block. This is the same behavior as in Sublime Text and TextMate which use the same language grammars.
Textastic is already configured to be able to open all text files, but if a file extension is not registered in the system, iOS does not know that it is a text file.
So it looks like the ".config" file extension is not known to the system so that it doesn't know that it is a text file and thus won't open it in Textastic.
So it looks like the ".config" file extension is not known to the system so that it doesn't know that it is a text file and thus won't open it in Textastic.
Auto-indentation is already in the Mac version and I plan to add it to the iOS version, too.
You can try to use the built-in "ASP vb.NET" syntax definition.
You can also add custom syntax definitions to Textastic by using TextMate bundles. See
You can also add custom syntax definitions to Textastic by using TextMate bundles. See
A quick search for "vbscript tmbundle" in Google brought up this TextMate bundle which should work:
This is not really the right forum since it is for the Mac version of Textastic, but anyway: Currently, the iOS document picker only supports opening a single file/document, not a folder. However, I'm working with the author of Working Copy to find workaround.
For local preview, Textastic basically loads the file similar to the file:// protocol in a desktop browser. Browsers do not store cookies for local files. I'll consider using a full HTTP server for local preview in a future version of Textastic.
Yes, the Firebug integration could be better. I'll try to improve this in future updates.
Customer support service by UserEcho
