Files left open after closing.
Alice Bevan-McGregor 10 years ago • updated by Alexander Blach (Developer) 9 years ago • 3
Exported some YAML data from my database, had a quick gander and search through it in Textastic, closed the file, trashed it, and now I can't empty the trash until I restart Textastic (and lose my carefully configured workspace layout) as the file is left open even after being closed.
This is a bit of a problem that I've often encountered with numerous programmers' editors. I've even immortalized one of the bugs using a meme. ;P
Customer support service by UserEcho
I'll look into it.
What I don't understand is this part: " (and lose my carefully configured workspace layout) "
Textastic should restore all windows, their positions, sidebar content and open tabs/files when it is restarted.
Due to the fact that my development environment automatically reloads source code when the files change on-disk I have globally disabled Apple's new autosaving feature; it was causing nothing but headaches due to syntactically incorrect files being saved on a regular basis. Also, due to window restoration behaviour being extremely aggravating in 90% of the applications I use—notably development tabs in Safari and the many tabs I have in Terminal being restored incorrectly—I have also enabled the "close all windows on application quit" option.
The latter window restoration problem is a weird one: Terminal tries to track the current working directory of each window, but due to the fact that I'm using virtual chroots and some advanced zsh trickery to isolate work environments it never gets this right. Ever. ;)
Edited to add: I do appreciate the options; for end users who only really need to worry about e-mails, desktop publishing documents, etc. I can wholeheartedly recommend full restoration and autosave. But not for a developer such as myself.
Ah, ok, I see :)
This will be fixed in the next update.