Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#38346 - [qcad] relative paths in ECMA scripts are wrongly resolved
Attached to Project:
Community Packages
Opened by Hanspeter Portner (ventosus) - Wednesday, 01 January 2014, 22:12 GMT
Last edited by Sergej Pupykin (sergej) - Wednesday, 08 January 2014, 11:43 GMT
Opened by Hanspeter Portner (ventosus) - Wednesday, 01 January 2014, 22:12 GMT
Last edited by Sergej Pupykin (sergej) - Wednesday, 08 January 2014, 11:43 GMT
|
DetailsDescription:
When running QCAD with a custom ECMA script via the '-autostart' command line, a call to the ECMA function 'getAbsolutePathForArg("./")' should return the absolute path of the folder the script is in, e.g. '$(pwd)/./test.js', but instead the function always returns '/usr/share/qcad/./'. This makes it impossible to dynamically load files using relative path prefixes './' and '../'. Steps to reproduce: qcad -autostart test.js Steps to fix: Do not cd into /usr/share/qcad in /usr/bin/qcad shell script (see patch for PKGBUILD) |
This task depends upon
rel_path_ECMA_script.patch