+4

How to hide/disable new tab UI feature

Gary 12 years ago updated by Abhi Beckert 6 years ago 3 1 duplicate

Hi, how do I hide/disable the new tab feature if I don't want it? I usually manage several single document windows side by side and aim for maximum vertical space, having a single tab UI chrome eating space at the top of a document is rather distracting. Thanks --Gary

+4
Fixed

command delete

Izaak Miller 12 years ago updated by Alexander Blach (Developer) 12 years ago 2

Textastic doesn't appear to support the OS X default behavior for "command + delete" which will delete from the cursor to the beginning of the line. 

Answer

Will be available in v1.1.

+4

convert tabs to spaces / spaces to tabs

Robert Crooks 10 years ago 0
I meant to put this in Mac, not iOS section, though it would fine to have it for the iOS version also

Option to convert all tabs to spaces (or vice-versa) for a selection or the whole document
+3

Side by side File compare feature ala vim -d

Jmm 5 years ago 0

Side by side file compare like the vim -d feature.

+3

Liquid Syntax

Arthur Freitas 5 years ago updated 5 years ago 1

It would be nice to have better Liquid markup support.


There are already some bundles for it, but this one is the only one that works with Textastic, and it has some bugs like `<script>` blocks not being recognized like it happens with the HTML syntax.

Thanks!

+3

Can you please make links contained in the text clickable? Rright now they are only highlighted. Thank you Alexander.

LeeB 7 years ago 0

Can you please make links contained in the text clickable? Rright now they are only highlighted. Thank you Alexander.

+3
Under review

Help with Regex find/replace backreferences

Kerim Friedman 9 years ago updated by Bjarne Dein 4 years ago 3
I've seen Regex handle finding and replacing backreferences in different ways, but I can't figure out how it works in Textastic for Mac and there isn't any documentation that I can find. Below is a discussion from a Regex tutorial website. None of the methods discussed seem to work for me.

> Numbered Backreferences

> If your regular expression has named or numbered capturing groups, then you can reinsert the text matched by any of those capturing groups in the replacement text. Your replacement text can reference as many groups as you like, and can even reference the same group more than once. This makes it possible to rearrange the text matched by a regular expression in many different ways. As a simple example, the regex \*(\w+)\* matches a single word between asterisks, storing the word in the first (and only) capturing group. The replacement text <b>\1</b> replaces each regex match with the text stored by the capturing group between bold tags. Effectively, this search-and-replace replaces the asterisks with bold tags, leaving the word between the asterisks in place. This technique using backreferences is important to understand. Replacing *word* as a whole with <b>word</b> is far easier and far more efficient than trying to come up with a way to correctly replace the asterisks separately.

> The \1 syntax for backreferences in the replacement text is borrowed from the syntax for backreferences in the regular expression. \1 through \9 are supported by the JGsoft applications, Delphi, Perl (though deprecated),Python, Ruby, PHP, R, and Tcl. Double-digit backreferences \10 through \99 are supported by the JGsoft applications, Delphi, and Python. If there are not enough capturing groups in the regex for the double-digit backreference to be valid, then all these flavors treat \10 through \99 as a single-digit backreference followed by a literal digit. The flavors that support single-digit backreferences but not double-digit backreferences also do this.

> $1 through $99 for single-digit and double-digit backreferences are supported by the JGsoft applications, Delphi,.NET, Java, JavaScript, VBScript, PCRE2, PHP, and XPath. These are also the variables that hold text matched by capturing groups in Perl. If there are not enough capturing groups in the regex for a double-digit backreference to be valid, then $10 through $99 are treated as a single-digit backreference followed by a literal digit by all these flavors except .NET, Perl, and PCRE2.

>Putting curly braces around the digit ${1} isolates the digit from any literal digits that follow. This works in the JGsoft applications, Delphi, .NET, Perl, PCRE2, PHP, and XRegExp.

http://www.regular-expressions.info/replacebackref.html
+3

Splitting view vertically

Niklas Modin 11 years ago 0
It would be great to be able to split the text view vertically. For instance working on a .h and .c file at the same time and being able to see both files at the same time without the need to start two instances. Also very useful when comparing files.
+3
Fixed

Double click and drag should keep selection from double click and add to it with the drag.

JakeCarter 12 years ago updated by Alexander Blach (Developer) 12 years ago 2

1. Double click and hold over some text. Note that what is under the mouse is highlighted.

2. With the mouse button still 'down', start to drag right to add the next word to the selection.


Expected:

The doubled clicked selection should remain and the next whole word should be added to the selection.


Actual:

The selection will start as if you never double clicked. It will start from where your drag started.


+3
Fixed

Default Application

Keith Smiley 12 years ago updated by Alexander Blach (Developer) 12 years ago 2

After installing Textastic it made itself the default application for many code-related file types/extensions. I think this is terrible behavior. This overrides all the default applications that the user has set, possibly different applications set for different extensions. When I install a new application regardless of what it is I _never_ expect it to set itself as the default for any file type (obviously excluding applications that create their own file type). No other text editors on OS X seem to do this nor does the only other similar type of application I can think of, photo editors. I believe this behavior should be removed and allow the user to deal with setting Textastic as the default applications for the extensions they choose.


Answer

Will be fixed in v1.1.