Question about new filename_dialog

[Eddy De Greef]

Joerg Fischer wrote:
> Eddy De Greef wrote:
>> It probably is Lesstif/Cygwin related, because everything seems to work 
>> fine with Motif.
> 
> Could it be that it is Cygwin only? There were changes like the
> fix for SF bug #1345424: externally changed file status not recognised.
> The file's uid and gid are now recorded too to detect any changes.
> 
> I investigated a bit further. If you have a Untitled window and click
> save and now choose a file that exists *and* is already open in another
> nedit window/tab, then clicking on yes overwriting is ok, you can almost
> go to sleep until the other dialog box which tells you that the file is
> already open (so cancel or close the other tab) appears.
> 
> Perhaps the thing is that Cygwin just emulates the Unix file system. I'm
> quite certain that such a time delay wasn't there in former nedit versions
> under Cygwin.

I have never used Cygwin, but I would rather expect it to be some 
X-related problem. I vaguely remember that there used to be a bug in 
Solaris' Motif that also resulted in some long delays when dialogs had 
to pop up.

You can add print statements with timestamps to the code. Eg:

   time_t mytime;
   time(&mytime);
   fprintf(stderr, "%s now calling foo()\n", ctime(&mytime));

It's tedious, but with a binary search you should be able to narrow it 
down pretty quickly (if you are a bit familiar with the source code).
It is probably best to run nedit in synchronous mode (-synchronous) if 
you want to try this.

Eddy