+1

Which regular expression engine?

Benct Philip Jonsson 12 years ago in General updated by Benct Philip Jonsson 9 years ago 3
Thanks for a great app! I have some questions regarding regular expressions, though:

- Which regular expression engine does Textastic use?
- Where can I find the syntax spec?
- What is the right syntax for including captures in the replacement text?
- Can I use case modifiers like \U \L \u in the replacement text?

TIA for the answer which I hope end up in the FAQ/manual! (Is there a FAQ distinct from the manual?
+1

It works great with the Logitech bluetooth keyboard. Any chance your going to eventually add open file tabs to the gui ?

greg traub 13 years ago in iPad updated by Alexander Blach (Developer) 13 years ago 1

It works great with the Logitech bluetooth keyboard. Any chance your going to eventually add open file tabs to the gui ?

+1

Nicely done.

AChron 14 years ago updated by Alexander Blach (Developer) 14 years ago 1
Mein erster tag mit Textastic. Ausgezeichnete arbeit.

From the content of the forums, I am eagerly awaiting version 2.0. (If the German portion is awful, I blame babelfish...)
+1

Folders to organize connections

Alexander Blach (Developer) 14 years ago 0
Can we have folders to manage a long connection list? e.g. I might have a folder for client connections and a folder for internal connections.  It would be nice to be able to manage the connections a bit better.

(feature request received by email)
+1
Thanks

Great :D

Myako Toudai 13 years ago updated by Alexander Blach (Developer) 13 years ago 0
Hey Alex,

I know I'm nerving all time with my parser/syntax check ideas. But I've got an iPad2 and Textastic runs very smooth on it. I code on it in javascript and can run it in the internal web engine... very cool and nice for my html 5 game project. :D

Overall it is a really great editor and very well supported by you.
Thank you for that nice piece of software.

Greets Alex (Tapsi)
+1

crash on new ipad

晋威 黄 13 years ago in iPad updated 13 years ago 8

don't know why it always crash on new ipad, ver 5.1.

textastic version is the latest ipad version v4.0.2.

+1

Edit selects current file

Amafirlian Freaniathem 13 years ago updated 13 years ago 4
When selecting 'edit' it would be great if the current file was automatically selected. Especially with long file names (e.g. Created after using the 'textastic:' custom URL scheme) that are only partially visible it is sometimes difficult to find them again (e.g. When using edit to rename them to a shorter file name).
+1
Under review

Longer tab widths

Ted Chew 10 years ago in General updated by Ken_P 6 years ago 2
It seems the tab width currently tops out at 8, but this is insufficient for certain programming languages. Assembly languages in particular can have instructions of more than 7 characters. That means the instruction arguments will no longer line up in a column making the code difficult to read. I use a tab width of 12 in those cases, though ideally, it would be possible to enter any width within reason
+1
Started

App is crashing every few minutes

Althea Jones 13 years ago updated by Alexander Blach (Developer) 13 years ago 8
App is crashing every few minutes, most often when deleting several lines of text by holding down the delete key but also happened when I was simply scrolliing down the code page. I've tried rebootting the ipad but no difference. Had been working fine until recently (I have not updated to the retina-display version, so I'm using the one before that). I've really come to rely on this app for my paying job., so I sincerely hope you can fix this!
Answer
I think I found the bug - it was in the code that caches highlighted lines and only occured in files with more than 500 lines. 

It will be fixed in the next update.
+1

Show all whites paces as what they are - non-space whites pace issue.

Martin S. Stoller 13 years ago updated by Alexander Blach (Developer) 13 years ago 1
Great app! One issue though - when I paste code from the iPad integrated email app into Textastic, I sometimes get non-space white spaces, that end up breaking JavaScript or HTML in some browsers. Maybe a feature to see what white spaces are not actually space?