Franz Haeuslschmid <lukrez <at> gmx.at> writes: > > Mike, > > I think I've found the reason for XFig's strange behavior.
Franz - Well, you got further with the source than I did! Once I saw that (a) xfig always created files of the same name (based on the PID), (b) that file remained throughout the xfig session after an EPS import, and (c) that I was never able to see the file after doing the same with xfig running on Linux (since, as you discovered, it should get immediately deleted once xfig has used it!), I figured it was a windows filesystem/permissions type problem that was beyond my expertise and that I was unlikely to get much help with since (i) the majority of xfig users likely run it happily on *nix, and (ii) it appears that there aren't many cygwin users (i.e. 2 at the moment!) who find the problem an annoyance ... BUT, thanks to your curiosity and subsequent investigations, it seems that we may have an answer. Franz Haeuslschmid <lukrez <at> gmx.at> writes: > On the other hand, I'm wondering why `unlink' doesn't remove the > file as it should do. I'm afraid I'm not going to be of much help to you here ... ;-) Looks like I'll have to get the X11 development stuff installed on my box when I get back to it to try your idea. Thanks for your efforts - I'll let you know how it goes. Cheers, Mike -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/