You should collaborate with a-Shell app to use it as an external debug console.

a-Shell is an amazing environment that simulates the same shell of the Mac(Darwin) on iPad / iPhone and let the user run and debug all interpreted languages (because Apple forbids apps to compile binaries). But for javascript, wasm, Python, etc. a-Shell behaves exactly like a shell, running code in Javascript, wasm, Nodejs, Python, etc and debug it. But a-Shell lacks a visual text editor, and Textastic could be its perfect companion. 

It just need the following features:

- a button to immediately run/debug a python script in a-Shell (a-Shell allows to select and unlock writing/reading permissions on any iCloud Drive or iPad folder), opening a-Shell and running a dynamically generated bash script to run the python code with arguments.

- specify multiple launch properties when debugging/running the code, generating a bash script to open in the source file folder with a-Shell (for example first clean the file with Black, then run it with the parameters specified in the launch properties config). Multiple launch configurations should be stored for each file.

- Using the bash script passed to a-Shell, give the option to save the console error output in a error.log file with a date that can be opened or kept open by Textastic.

- On iPad there should be the amazing option to run a-Shell window and the Textastic window side by side! Coding and instantly see the script running!

Please, consider this!

Feature suggestions for Textastic
Thank you for a GREAT APP! For many of us the ability to use our tablets for coding is very important. It almost can't be done on Apple devices without using TEXTASTIC! (Which works seamlessly with WorkingCopy). The following is just a suggestion for upcoming added features...not sure where else to send it?
1. I would very much like to see a quick access button that lets you turn on and off 'read only mode'. This option currently exists but is not readily available. This needs to be a button you can tap that is visible on screen while in program code edit mode, and be available for each screen opened on a iPad Pro while using split screen. This would facilitate using one code window for one version of a program or for seeing a function in one section of the program so it can be compared to the same program code perhaps in a different section of the code, to allow editing of the part you are working on but not allowing inadvertent changes to be made to the code in the other panel which could happen while coding in the wee hours of the night, falling asleep at the wheel and inadvertently touching the side of the screen you don't want to make changes to. Believe me this happens, and finding an inadvertent 'addition' like a ; that stops the program running in its tracks, etc can be very difficult!
2. A way of marking functions in the labels/symbols list so you can easily jump back and forth between sections of your code. In a long program, the symbols list can be quite lengthy making it hard or time consuming to say find a function at the bottom of the code to compare to a function at the top of the code. If these function labels could be 'pinned,' one after the other in a separate section at the top of the list, it would facilitate quick access to different sections of the code, while making changes or comparing the different sections of the code. (Invaluable for trouble shooting!)
3. Highlighting closing brackets that are connected to one another. For example in Java Script, with many brackets, keeping track of which brackets belong to what can be very difficult and time consuming. I would also suggest automatic labelling of the closing bracket with a comment that reflects the 'name' of the function or IF statement the bracket is associated with. Along the same lines being able to highlight in colour an entire function would be very helpful in keeping straight what function you are working in after the code gets so long you can't easily see the start of the function without scrolling to it.
4. A trace route capability to trace the path of the code as each line executes to facilitate trouble shooting.
Thanks again for a great app and all the effort you put into it. Textastic makes writing code on an iPad Pro or even a less featured iPad possible. Who needs a desktop anymore!!
Doug Dyer

Hi, before iOS11 Beta, I used to open WorkingCopy repos with the "Open ..." Menu.

On iOS11 the Open  menu now opens the new Apple App "Files". In Files you can pick WorkingCopy again, but the PopUp with the WorkingCopy repos does not contain a Pick button, so I can not open the repo in Textastic. Same procedure works in GoCoEdit.

say i am looking at file.c:49 and i search for symbol x in the file and jump sroumd to random occurrences, I would like the ability to jump back through each jump. Lets say occurences i view in order are file.c:10 then file.c:200.

The featre request would be a button or shortcut (maybe cmd + [, ]) that would take me through the stack in the following way:

from current position: file.c:200

hit back, end up at: file.c:10

hit back, end up at: file.c:49

hit back, stack empty, noop

this would extend to multiple searches and across files. you have to handle files edited between traverals of history, but just document the behavior.

I'd like to add some custom Emmet snippets to Textastic on iOS, but I can't make it work.

I tried following the directions on Emmet's site for adding the file (https://docs.emmet.io/customization/snippets/), but I'm not sure where to put it. I've added the snippets.json file to #Textastic, but it won't take.

Is it possible to use this file right now? Does it need to go in a subfolder of #Textastic?