Yes, maybe there is a problem with samba and Maverick since I changed to Maverick almost at the same time I change to TextMate v2. I try opening with another editor and I get a non updated version of the file.
Then I try to open with TextMate and I get the message "TODO Reselect previously open document". I cannot open the file with TxtMt until I close my session on the OS and I log on the OS again. However, after a while, I can correctly open the file with other editors.
Is there a way to do a "clean reopening" of the file without having to restart my user session in the Mac OS?
Another issue I have notice is that TxtMate does not detect automatically changes in files of samba file system.
2013/12/19 Allan Odgaard mailinglist@textmate.org
On 18 Dec 2013, at 21:54, Jesús Baquedano wrote:
[…] I occurs only when using subversion […] file is in a linux machine
and I use samba to access it from TextMate […] I see the file in TexMate. The file is incomplete. The last lines are lost […]
Sounds like it could be a problem with the network file system, especially since you re-open the file in TextMate and still see the last part missing, i.e. the network file system locally cached the file prior to it having been fully written by subversion.
Did you try to open the file with another application?
You mention the file being open in TextMate while updating it on the linux server. What if you close the file before updating it (TextMate keeps the file open for “events only” to be notified about changes, perhaps this plays a role in the network file system’s behaviour)?
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
On 20 Dec 2013, at 16:38, Jesús Baquedano wrote:
[…] Is there a way to do a "clean reopening" of the file without having to restart my user session in the Mac OS?
If the issue is with the samba file system driver, then I assume what you want (and achieve by restarting the user session) is to basically “reset” the driver’s state. This might also be doable by unmounting and mounting the volume.
Another issue I have notice is that TxtMate does not detect automatically changes in files of samba file system.
TextMate uses the kqueue API to be notified about file system changes. There is a good chance this does not work for some network file systems (though it does work for AFP).
An alternative would be to have TextMate regularly stat the file, I might add that in the future, but if your network file system return stale/cached data (as it appears from what you write) then this might not make any difference.