From the release notes:

• Compatible with TextMate and Sublime Text 3 syntax definitions and themes 

I've tried dropping my .sublime-syntax file into the #Textastic folder, but I'm not getting the option to use it. It works fine on Sublime.

I just bought Textastic for my ipad. I want to use it to edit plain text files, such as LaTeX documents with .tex extensions. My files are in Google drive, and while I can browse to the folder, the files with the .tex extension are grayed out and cannot be selected. What should I do to make .tex file (or any plain text file) recognizable to Textastic?

I would me honest - copying files to Textastic, I mean copying, not opening - is a huge pain in the ass. I overcome this only by "share to" button, when I need to copy .tmBundle files to Textastic iCloud folder, so it could be moved in proper folder inside Textastic.

Thanks!

中文注释显示的都是乱码,不知道该怎么办?

seems on iPad keyboard is dismissed (closes) automatically every few seconds, and focus lost. How do I permanently “pin” the keyboard

I would love to see better support for iOS 11 files app integration and syncing.

subj

I'm currently unable to open Dropbox folders using the "Open..." Files app integration. If I tap "Select", select a folder full of text files, and then tap "Open", I get an error dialog saying the following:

> The plug-in returned an error.

>

> The file doesn't exist.

> The operation couldn't be completed.

> (NSURLErrorDomain error 404.)

Is there no support for this? I was able to get a folder from "Working Copy" open in this manner, which is nice, but I would also love Dropbox support for this.

I want my money back. I want back to my legacy Textastic app.

Textastic Pro is buggy. I got A lot of errors opening A folder in Dropbox.

Transfer error.
The operation couldn’t be completed.
(TJDropboxErrorDomain Error 0.)

The feature with keeping remote links for uploaded/downloaded files is awesome. Can you extend it to folders and recursivelly to all files within. So that when one uploads/dowanloads a folder, all files inside get a link, and whenever one of the files changes you can simply upload it to your server to build and execute?

This way the workflow for working with repository code would be the following. Open the repo folder from WorkingCopy, upload the folder to SFTP server (or whatever), do changes, upload, build, run, test on the server, commit in WorkingCopy, push.

Many thanks