Thanks! I'll think about it.

I already have this implemented in the Mac version of Textastic and I do plan to add it to iOS eventually. I'm just not sure about the UI - i.e. were to put a button to invoke it in addition to a keyboard shortcut. Suggestions are welcome! :)

Hello,

this is a problem when opening files from Google Drive using the "Open…" command in Textastic. This invokes the iOS document picker and uses the Google Drive file provider extension of the Google Drive app. Unfortunately, the Google Drive app has some bugs.

Instead, please use the remote transfer screen of Textastic: tap on the "globe" button in Textastic and create a new Google Drive connection. You can then download and upload files using this connection. It also allows you to download whole directory trees.

It's basically the same functionality as for Dropbox, which is explained here:
https://www.textasticapp.com/v6/manual/lessons/How_do_I_access_files_in_my_Dropbox_account.html

Yes, exactly. Textastic 6.3.1 uses the latest version of libssh2 which supports more ciphers.

I don't think you can disable it when click on the Dock icon. Yes, with Cmd-Tab it works.

You can change that behavior, too: if you want that Textastic opens a new untitled file instead of the open dialog, you can use this command:

defaults write com.textasticapp.textastic-mac NSShowAppCentricOpenPanelInsteadOfUntitledFile -bool false

Apple recommends that apps support both Automatic Termination and Sudden Termination. That's what Textastic does.

Other apps probably do not use the official system mechanism for closing the app when the last window is closed but use a custom solution/hack.

With Textastic I try to follow Apple's best practices as much as possible.

You can disable Automatic Termination system-wide using the command line:

Disable Automatic Termination in Mac OS X
Launch Terminal and enter the following defaults write command:

defaults write -g NSDisableAutomaticTermination -bool yes

Re-Enable Automatic App Termination in Mac OS X
You can always reenable the default behavior of OS X and turn auto termination back on:

defaults delete NSDisableAutomaticTermination

I copied the instructions from this article: http://osxdaily.com/2012/05/15/disable-automatic-termination-of-apps-in-mac-os-x/

Actually, Textastic tries to use macOS standard behavior as much as possible. What you are seeing is called "Automatic Termination". It was introduced in macOS 10.7 Lion. If you close the last window and then switch away from the app, the app is closed automatically.

This is a snippet from the developer documentation:

Automatic and Sudden Termination of Apps Improve the User Experience

In OS X v10.7 and later, the use of the Quit command to terminate an app is diminished in favor of more user-centric techniques. Specifically, Cocoa supports two techniques that make the termination of an app transparent and fast:

• Automatic termination eliminates the need for users to quit an app. Instead, the system manages app termination transparently behind the scenes, terminating apps that are not in use to reclaim needed resources such as memory.
• Sudden termination allows the system to kill an app’s process immediately without waiting for it to perform any final actions. The system uses this technique to improve the speed of operations such as logging out of, restarting, or shutting down the computer.

Automatic termination and sudden termination are independent techniques, although both are designed to improve the user experience of app termination. Although Apple recommends that apps support both, an app can support one technique and not the other. Apps that support both techniques can be terminated by the system without the app being involved at all. On the other hand, if an app supports sudden termination but not automatic termination, then it must be sent a Quit event, which it needs to process without displaying any user interface dialogs.

Automatic termination transfers the job of managing processes from the user to the system, which is better equipped to handle the job. Users do not need to manage processes manually anyway. All they really need is to run apps and have those apps available when they need them. Automatic termination makes that possible while ensuring that system performance is not adversely affected.

Apps must opt in to both automatic termination and sudden termination and implement appropriate support for them. In both cases, the app must ensure that any user data is saved well before termination can happen. And because the user does not quit an autoterminable app, such an app should also save the state of its user interface using the built-in Cocoa support. Saving and restoring the interface state provides the user with a sense of continuity between app launches.

For information on how to support for automatic termination in your app, see Automatic Termination. For information on how to support sudden termination, see Sudden Termination.

https://developer.apple.com/library/content/documentation/General/Conceptual/MOSXAppProgrammingGuide/CoreAppDesign/CoreAppDesign.html