Thanks - I was going to do something like that initially, but after moving the file, I wanted to be 'done' with that file if it make any sense?

Right now, I'm going to try and write up something that just opens the next file in the directory, and if there are no more files, then just an empty file.

Yes I am. Thanks for the update.

It's currently not possible to control keyboard visibility via workflows or scripts, sorry.

In my case I can also do an Undo followed by a Redo to eliminate the flickering.

Hope that helps.

@omz

Thanks!
I am glad if you correspond some day...

Have a look at the Workflows directory:

+1 : That would be great!

Thanks, that saved my day for the "transfer to Dropbox" problem.

Deleting local files is relatively easy via Python (e.g. os.remove(os.path.expanduser('~/Documents/myfile.txt')), but deleting Dropbox files isn't really possible, at least not without pretty significant effort (using the Dropbox API).

Btw, if you want to delete a local file that is currently open, you should open a different file first; otherwise, the editor would automatically save a new file.

Thank you. Just saw it in a Youtube Video.

Yes, I've seen this too, it seems to be related to iOS 7, it never happened on iOS 6 afaik, but it's not always reproducible, so it's kind of difficult to fix, though I have some ideas for workarounds.

I've made a little demo workflow using @lrr's approach:

http://www.editorial-workflows.com/workflow/5874785116487680/QxP96UHBH-o

If you use the dark theme, you might want to adjust the CSS colors in the Show HTML action.

Also, FWIW, I was running iOS 6 (NO jailbreak) on an iPad Mini when I saw the crashes. The only way to get around it was to kill editorial and restart it (it would still be in the multitasking list after the crash), but even that wasn't 100% reliable.

Ed

You want to use python (not workflows)?

PDF created by PIL is big and not searchable.

DocVerter requires an internet connection.

Currently I use this workflow with this app.

Peter has more ways.

A prefix might be an option, I could imagine using something like var-xyz=foo to set the variable xyz... I probably won't change the URL scheme in the next update, but I'll keep this in mind.

Very glad to see this new addition! Looking forward to the insights people will share.