<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8">
</head>
<body>
<div style="font-family:sans-serif"><div style="white-space:normal">
<p dir="auto">On 9 Feb 2017, at 4:16, Carpii UK wrote:</p>
<p dir="auto"></p></div>
<div style="white-space:normal"><blockquote style="border-left:2px solid #777; color:#777; margin:0 0 5px; padding-left:5px"><p dir="auto">I'm hoping a TM dev could point me in the right direction of where TM's<br>
inode caching takes place please?<br>
<br>
I'm struggling to find it, but I think it might be one of the sources of my<br>
issues using TM on a mounted remote filesystem</p>
</blockquote></div>
<div style="white-space:normal">
<p dir="auto">There isn’t any inode caching per se, however, when opening a file, TextMate will check if you already have that file open, and this check does involve looking at inodes.</p>
<p dir="auto">So a possible explanation for your issue <em>could</em> be that your virtual file system reuses inodes, and that you open a file that uses an inode of something you previously opened (but which had a different path), and is still open somehow, e.g. in a background tab.</p>
<p dir="auto">Perhaps you can ask the creators of the virtual file system that you are using, how they deal with inodes, i.e. if there is a high chance of inode re-use. If they say no, my theory is invalid, but if they say yes, then perhaps there is something to it.</p>
</div>
</div>
</body>
</html>