on Fri, Nov 21, 2003 at 10:35:38AM +0000, Dave Howorth (dhoworth@mrc-lmb.cam.ac.uk) wrote:
> There seems to be a problem with gv and filenames with spaces in them.
> I don't use it regularly but when I open a file whose name contains a
> space (e.g. 'junk space.pdf') and then try to print it, I see an error
> dialog:
>
> Failed to scan file /tmp/gv_whatever_junk space.ps.tmp
>
> (why do programs not let you copy messages from errors and instead force
> you to type them again!) and the following appears on stdout:
Try running 'strace gv 2>&1 | tdd gv.log' and looking at the dump.
> Error: /undefinedfilename in (space.ps.tmp)
> Operand stack:
>
> Execution stack:
> %interp_exit .runexec2 --nostringval-- --nostringval--
> --nostringval-- 2 %stopped_push --nostringval-- --nostringval--
> --nostringval-- false 1 %stopped_push --nostringval--
> --nostringval--
> Dictionary stack:
> --dict:1062/1123(ro)(G)-- --dict:0/20(G)-- --dict:68/200(L)--
> Current allocation mode is local
> Last OS error: 2
> GNU Ghostscript 7.07: Unrecoverable error, exit code 1
>
> I guess there's a configuration file somewhere in the debian package
> that is missing some quotes. Does anybody happen to know what the fix is?
>
> I run Woody
> $ gv -v
> gv 3.5.8 (debian)
If this is reproducible, mishandling filenames with spaces is a bug and
should be fixed. Check BTS and file if appropriate.
Peace.
--
Karsten M. Self <kmself@ix.netcom.com> http://kmself.home.netcom.com/
What Part of "Gestalt" don't you understand?
Please understand, I hold you in the highest respect.
- Princess Bride
Attachment:
pgpCb0t4PAgxw.pgp
Description: PGP signature