cannot open relative paths using script extensions from command line
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Inkscape |
Fix Released
|
Medium
|
Patrick Monnerat |
Bug Description
I am unable to open an EPS file from the comand line
$ inkscape -z -f drawing.eps -l drawing.svg
where drawing.eps exists in my working directory and is a valid EPS file. Inkscape tries to open it as an SVG file, which of course fails. When I instead use the command
$ inkscape -z -f `pwd`/drawing.eps -l drawing.svg
things work as I expect. I did some debugging and I believe my problem is with src/extension/
but the the name of the input file is left alone, so the input file is sought in the working directory, i.e. the directory where the extension script lives.
This happened to me with Inkscape 0.48.0, built from source on RHEL5. I also built python2.6 and the entire gtk+ stack from source and installed everything under my home directory as I do not have root.
I did not have this problem with Inkscape 0.47 r22583 (Mar 12 2010) packaged with Debian 6.0 (Squeeze).
Changed in inkscape: | |
milestone: | 0.49 → 0.48.4 |
Changed in inkscape: | |
status: | Fix Committed → Fix Released |
reproduced with Inkscape 0.48+devel r9986 on OS X 10.5.8