Hey guys, It seems that TextMate.save_current_document() is acting a bit weird. It does in fact save the file to the HDD but it doesn't update the 'state' of TextMate.
You can see this by the fact that the tab still displays the file as unsaved. A more pressing issue is that if you call TextMate.save_current_document() // do some work on the file on the HDD TextMate::rescan_project() it will display a warning showing that the file has been changed by another process while there were still unsaved changes in the buffer - But there were no unsaved changes as it had already saved the file in the ruby code. Is there a known work-around to avoid the message? Thanks, Mads Hartmann Jensen _______________________________________________ textmate-dev mailing list [email protected] http://lists.macromates.com/listinfo/textmate-dev
