Notepad++, Visual Studio, Visual Studio Code, and the iOS Notes app all allow you to scroll beyond the end of a file. This means that you can always scroll so far down that the last line of the file is not at the very bottom of the screen.

Both of the following screenshots show a file/note containing the exact same text, scrolled as far down as possible. The line "7. Quail" is the very last line; there are zero empty lines after it in either screenshot. Notice how, in Textastic, you're cramped right up against the bottom of the editor. In the Notes app, however, you can continue scrolling for about another half screen before you can't scroll anymore, which allows you to work in the center of the screen even when writing at the very end of the file.

I think it would be nice if Textastic also had this feature. It doesn't need to be the only option, or the default option. Notepad++, for example, allows you to enable or disable this feature in its settings.

Hi there, I have been around now for almost 10 years, waiting for code folding (matching brackets) since the beginning.
Is there still active development going on here? Any idea when you plan to implement this coders must have?

Looking forward to your feedback!

When using the floating keyboard on iPad (the one that doesn’t cover 50% of your screen) the additional keys row covers all UI elements and input on the bottom of the screen which makes the app effectively unusable.

I need a text editor for iPad that does vertical column blocking.

Textastic is a fantastic code editor. However, I’d like to be able to work on some of my android projects on the go using an iPad. TextAston doesn’t do anything for Kotlin (.kt) files. Would really love to see support for this in the future – would be extremely helpful since there are not really any options for android development on iPad at the moment. Thanks for all the work you’ve already put into this insanely great app!

After the iOS 16 update, Korean cannot be input properly.

When writing Korean, Korean is entered incorrectly.

For example, it should be entered as “한글”, but now it is entered as “하ㄴ그ㄹ”.