Your comments

You can find all existing code completion definitions (JSON files) that are included in Textastic at https://github.com/blach/Textastic-Customization/tree/master/CodeCompletion


If you want to modify code completion definitions, you can edit them and put them in the "~Library/Containers/com.textasticapp.textastic-mac/Data/Library/Application Support/Textastic/CodeCompletion" folder mentioned above. Textastic will pick up the changes at application startup time, so you have to manually quit the app. 


If you do not change the uuid, your custom file will be used instead of the built-in one with the same uuid. If you use a new uuid (you can generate one with the uuidgen command line tool), the code completion file will be loaded in addition to existing ones.

I'll consider changing the behavior or adding some options.

I meant Cmd-Shift-N to create a new window.
Dragging into the window will add the file path or file contents (depending on modifier keys) into the editor.

Dragging onto the dock icon is the same as File -> Open which adds a new tab. Dragging multiple files onto the dock icon opens the files in multiple tabs in the current window.

Press Cmd-N before you drag the file onto the dock icon if you want a new window.
Did you drag the file on the dock icon or into the window?

Well, Textastic uses Auto Save that was introduced in Lion. That's the standard behavior in modern Mac apps.


Can you configure Transmit to ask before it uploads changed files? 


If I disabled Auto Save, other features like Versions and iCloud would be disabled, too.

Thanks for sharing your use case. Currently there is no way to exclude certain files. There's a separate feedback entry for this at http://feedback.textasticapp.com/topic/107275-filter-exclude-files-to-download/