Mercurial temporary file nomenclature

[Jason Harris]

No I am not using inotify. Sorry, but something quite similar. I am using apples FSEventStream functionality, to get notified when changes occur in a directory. Then I can rescan that directory, but since that file goes wizzing, the stream handling catches this and I turn around and rescan the directory, which causes another file to whizz by, which I then rescan the directory for, which causes another file to wizz by and well you get the idea. Thus I have to try and interrupt this process...

I suspend watching the stream until my scan is done, then try to flush the queued up notifications, but I have to wait a bit for the notifications to clear before I can pay attention to them, and this waiting time can be variable... and well this whole process is kind of unstable. It works but, man I wish I could just have the temp files generated outside of the tree.

Cheers,
  Jason

On Apr 12, 2010, at 8:55 PM, Dirkjan Ochtman wrote:

> On Mon, Apr 12, 2010 at 20:49, Jason Harris <jason.f.harris at gmail.com> wrote:
>> I *strongly* second this. I am writing a GUI client on OSX, I have some really nasty hacks in there to try and detect when the files have changed but really changed, and not changed because that temp file was whizzing by. It would make things fantastically simpler for me if I could just locate these in /tmp/ or as Larry says if this could be an environment variable. Anything but inside the repository tree, since this is the *very* tree I am trying to monitor for changes so I can figure out when to post status updates.
> 
> Huh? Are you actually using the inotify extension on OS X?
> 
> Also, don't forget to CC the list.
> 
> Cheers,
> 
> Dirkjan