Textastic for iOS / Textastic

0

Under review

External CSS not evident in preview iPad Pro

10 years ago in iPad • updated by 10 years ago • 1

I am running IOS9.1 on an iPad Pro. Filing in iCloud. Have html and style.css in same folder. Have correct <link> tag with reference to stylesheet. HTML+CSS does not preview in Textastic, but does display correctly when opened out of iCloud Drive in MAC Safari.

<html>
<head>
<title>How a Feral Monk Thinks - Part 1 of 12</title>
<link rel="stylesheet" type="text/css" href="gianni_custom2.css">
</head>

Vote

0

Under review

Editing imported files

11 years ago • updated 11 years ago • 4

Hello!
I've found a strange problem when I am trying to edit a file imported from the other app through "Open in". Any modification of such imported files gives me a "Cocoa error 513" and all changes get rejected. Also in app's local files menu appears new folder called "Inbox" that for some reason can't be deleted. But imported files any way go to the root of local files despite going to that inbox folder.
All files created directly in app's editor work fine, the problem only occurs with imported files.

Vote

0

Copy a Find result to the clipboard?

12 years ago in iPad • updated by 12 years ago • 1

Hello,

Is the a way to copy a Find result to the iOS clipboard? Want to quickly clip out a segment of HTML code and paste it into a WordPress blog post. The code segment will always match the following regex string:

The Find result highlights the text I want to copy to the clipboard. Is there a way to get Textastic to copy the highlighted text to the clipboard?

I don't see a way to do so. Any help will be appreciated!

Thanks & Enjoy life,

Steven

Vote

0

Latex symbol

12 years ago • updated 12 years ago • 4

Lately I have been using textastic as a LaTeX editor. So most of my LaTeX documents have user defined environments that I use. I have collected and made a handful to speed up my writing time. There is an odd issue with LaTeX symbol recognition with section/subsections from user defined environments using the \newenvironment{} command. As they are not even recognized. I am guessing that the current parsing algorithm does not even consider these situations. I have a hunch that this cannot be easily fixed, but I am still curious as to the likelihood of such a fix.

Vote