To the Developer,

I’m using Textastic everyday on an iPad. The layout of the interface, and how it works, is great!

Here’s what I’ve come to appreciate while working on Textastic all day:

1. When adding code files. the list of filenames scrolls to keep my filenames in the center of the list.

2. The + in the lower left to add new files is very convenient.

3. The keyboard shortcuts, such as:

     a. Cmd option p to toggle back and forth between output and the code editor.

     b. Cmd B to open and close the sidebar.

Those are just a few of things which save me time and make Textastic easy to use.

It’s obvious to me that a lot of thought—and probably listening to feedback—went into the interface.

The more I use this app, the more impressed with it. It is so accomodating—it’s a programmer’s dream editor.

Thank you, Alexander Blach, once again!!  Your app and your code is really good, excellent even!

Sincerely,

John

Hi, love the app, one feature request that seems obvious to me and would turn Textastic into a fantastic mobile mini-IDE:  it would be great if GCC error output in file:line:column format (as in below) in the Textastic Terminal was tappable to instantly jump to the given line and file, provided that a file with the same name is already open in a Textastic tab.

test.cpp:408:2: error: …

Hi Alexander,

Can we have the ability to unwrap individual tabs? When I'm on the iPad and I have split view with the 1/3 split on the right, I'd like to not have that page/tab word wrapped. But I'd like to keep the larger left split wrapped. 

Thanks!

Tom

Step to reproduce

1. Install textastic
2. Open localfile
3. Terminate all app
4. Reboot
5. Enabling airplane mode
6. Open textastic
7. Prompt about internet
8. Open app with no data collected
9. No prompt about internet

Pressing hide keyboard was repetitive to show top bar when doing quick edits of many files.

What happens currently? Does the content of the editor update? If the user has made changes - ie the are one or more undo objects - then display a message indicating an edit conflict? Maybe save the current (older) document to an alternate filename if there is a conflict.