Hi, Alexander, I have never experienced this type of situation. There’s no problem, I just wanted to know. That’s exactly what I want, so many thanks. Is there something that you or I could do to help make the process of conflict resolution easier, that is to help the user to integrate the changes/differences into one of the documents?

Alexander, could we also have a feature to go to column n on the current line, and perhaps go to line n + column m?

Could we revive this idea, the idea of a per-file readonly lock flag? I can see it might be a bit awkward, there are a number of very different ways I can think of to implement it, but then I know zero about ios so I don't know what I'm talking about anyway.

I note an earlier similar _sounding_ bug report concerning iPhone. This was tested on an iPad Pro large screen. FYI - Disimissing the onscreen virtual keyboard doesn't cure the issue, as the same problem still occurs within a taller match list which reaches to the bottom of the full screen if the list of matches is sufficiently long.

Any thoughts on some of these possibilities? A per-file read-only marker would be fantastic. And just something to duplicate an existing document easily so I can safely work on a new copy of a doc without overwriting the old version would be great. It would be very good if I could get Textastic to create a working copy of an existing document with a new name of my choice by remote-controlling it using the URL command mechanism.

any thanks for thinking about this. Would it represent a lot of work?

If I could integrate a curl app with all kinds of iOS apps, including textastic, then that would be fantastic

t would be so much better if you could mark individual files as read-only, so you could protect a doc from accidental modification when you've finished working on something.

Would also be very good if you could do a SaveAs, to make a new non-read-only copy of a file with a different name. - perhaps I've just not noticed this?