Re: New file patch (was: Re: Just a Matter of Style (was: LaTeX file handling))

[Arnd Hanses]

On 12 Aug 1999 16:22:30 +0900, [EMAIL PROTECTED] wrote:

[...]
>> The warning recommends to close previewers (XDVI, gv, etc.: They all
>> lock LyX' tmp-files). After closing them, the tmp-files are cleanly
>> removed by LyX.
>
>You are talking about opened files, not file lockings!  On OS/2 files
>opened by other processes cannot be removed.
>Please write a script which runs lyx and cleans up the /tmp if necessary.
>
>lyx
>test -d /tmp/lyx_tmp* && rm -rf /tmp/lyx_tmp*

Well, it was not only the garbage pile, there was also a wierd problem
with ocasionally impossible updating of a (blocked/opened) /tmp file
which made xdvi crash. My guess is, sometimes the file is first
removed/truncated by LyX, then rewritten. A warning to close xdvi,
triggered by EACCES errno solved the problem. 

But certainly it would be cleaner to investigate, what is happening
internally within LyX before fixing something.

        Who's the LyX file guru? How exactly is LyX designed to behave
when updating dvi? (In particular: What are the flags used for the
output Lib C functions ? Is always class FilePtr used or is this
occasionally bypassed?)

Greets, 
        Arnd