Lars Gullik Bj?nnes writes: > "R. Lahaye" <[EMAIL PROTECTED]> writes: > > If there's no signal sent, then what is supposed to be the actual > update-trick? Maybe that can help find the culprit. > > xdvi and gv watch the file to see if it changes. then reloads. > note that xdvi somethings needs some "event" f.ex. getting focus to > update, and gv needs some time.
So, is the following the correct conclusion? View->Update->Blabla, should take care that the corresponding blabla-file in LyX-tmp directory is regenerated, if necessary. It's then left up to the blabla-viewer, whether that will recognize the touched file and update its contents. If the blabla-file is NOT regenerated, then this is a bug in LyX. If the blabla-file IS regenerated, but not updated in the viewer, then this is entirely the problem of the viewer. Correct? ------------------------------ Assuming I'm correct, I can now try to solve the Update->Postscript viewing: Adding "-watch" to my gv viewer, solved the Update->Postscript viewing. So it's a gv-problem. Apparently my gv does not automatically watch the file, whereas it does on someone else's system. This must be related to the (default) setting of the GV.watchFile variable, either system wide (in e.g. /usr/X11R6/lib/X11/app-defaults/GV) or user defined (in ~/.gv). In my case this is set to "False" system wide (FreeBSD). However, we shouldn't and don't have to rely on this setting: just enforce that gv is always properly updating by adding the "-watch" flag to the gv Viewer command in lib/configure.m4. PATCH ATTACHED. Question: "gv" has a "-watch" flag. I don't know about "ghostview", but I suppose their behaviours are almost identical, aren't they? Regards, Rob.
configure_m4.diff.gz
Description: GNU Zip compressed data
