Textastic for Mac does support find in files. 

See Edit > Find in Files… or Cmd-Shift-F.

I'll consider adding TOML as a built-in language in a future update.

You can add custom syntax definitions to Textastic by using TextMate bundles or Sublime Text packages. See

https://www.textasticapp.com/v10/manual/customization/custom_syntax_themes_templates.html

A quick search for "TOML sublime text" on Google brought up this Sublime Text package which I just tried out and which seems to work fine with Textastic:

https://github.com/jasonwilliams/sublime_toml_highlighting

Please try the following:

• Go to https://github.com/jasonwilliams/sublime_toml_highlighting in Safari on your iPad/iPhone
• Tap the green "Code" button and select "Download ZIP"
• Unzip the file in the Files app. This will create a folder that contains the sublime package files. (Optionally you can rename this folder to "TOML")
• Move or copy that folder into the folder "On my iPad/Textastic/#Textastic/". This is equivalent to this folder in Textastic: "Local Files/#Textastic/".
• In Textastic, go to Settings -> Other and tap "Reload Customizations"

You can now select "TOML" from the list of syntax definitions in the File Properties.

Please note that this is a third-party syntax definition, not officially maintained by Textastic.

Here is a screenshot of how this looks in Textastic with a sample TOML document and the Vintage theme:

The SCP Wikipedia article links to the following 2019 quote of the OpenSSH team: "The scp protocol is outdated, inflexible and not readily fixed. We recommend the use of more modern protocols like sftp and rsync for file transfer instead."

Textastic already supports SFTP and I don't have plans to support SCP, sorry.

In case you don't want the app, you can request a refund from Apple on the following website: https://reportaproblem.apple.com

The macOS version and the iOS/iPadOS version of Textastic are two separate apps for two different platforms with different feature sets (the macOS version doesn't have remote connection support), so it would require two purchases if you want both.

The macOS version is available as a one-time purchase on the Mac App Store. A trial version is available on the website.

Textastic for iOS is a free download with in-app purchases. It offers a 7-day free trial when starting a monthly or yearly subscription, so you can explore all features before deciding to buy. If you prefer not to subscribe, a one-time purchase option is also available.

Offering a free download with in-app purchases is currently the most practical way to provide a trial through the iOS App Store.

Hello,

The link to the Mac manual is: 

https://www.textasticapp.com/mac/manual/ 

Granted, the Mac manual is outdated and hardly worth its name at the moment, but it is there. Where did you find a link that does not work?

The very detailed and up-to-date Textastic for iOS manual can be found at:

https://www.textasticapp.com/v10/manual/

And yes, Textastic for Mac does sync files with Textastic for iOS using iCloud Drive. Make sure to save your files in iCloud Drive > Textastic on the Mac and the files will sync to the "iCloud" location in the iOS app.

See: https://www.textasticapp.com/v10/manual/managing_files/local_files_icloud.html#icloud

I looked into it some more and could also reproduce the issue in Apple's TextEdit:

On macOS, Textastic uses the system's standard search implementation (NSTextFinder). Its "Full Word" option follows Apple's definition of what a "word" is. In this definition, a dot between letters is treated as part of the same word, rather than as a separator.

This is intentional and allows "Full Word" matching to work naturally for common text patterns such as:

• domain names like "example.com"
• file names like "document.txt"
• object or property names like "object.property"

Because of this, "document.documentElement" is considered a single word, while "document" or "document." followed by whitespace is not.

As a result, searching for "document" with "Full Word" enabled will match " document " and "document. ", but not "document.documentElement" or "document.addEventListener".

You can see the same behavior in Apple's TextEdit app.

At the moment Textastic does not (and cannot) override this system behavior. NSTextFinder is effectively a black box and does not allow this kind of customization.

If you need to find all occurrences regardless of word boundaries, please disable "Full Word" matching.