OK. Although not strictly a bug, I guess the fact that the browse button does not load the corresponding dialog field with the full path name is certainly very undesired behavior. The GhostView browser tries to be smart, and make nicer-looking filenames, but it badly backfires. So I think it is not so much more docs that are needed, but simply to fix this. And perhaps it is already fixed in the development version, with the home-made file browser. Unfortunately it would not be easy to port that patch to the v4.6.x branch, as it relies on infrastructure that only became available after large-scale refactoring of the X11 front-end. So it seems I must make a special patch to cure this in 4.6.3.. .