Re: [Gretl-devel] Function packages on Windows: new path permanently added

Am 12.10.2018 um 01:02 schrieb Allin Cottrell: Ah right, this must be it, my CWD is very likely currently set to that location. Good question. For me as a package developer it was actually useful, because when I debug and recreate the package it is then (in the CWD) automatically updated within gretl. Also this makes it easier to distribute non-public or non-official packages to colleagues, and also for backing them up along with other files. They just have to put it in the same place as their project. I was just not actively aware of it, but I don't think it's a hazard because shoving a package file actively in those non-standard places will be for some reason, not by accident. Also it's good that gretl shows the path where it found the package in its info window. It might be also useful to show that path in the package registry, but the space there is also limited. So probably just leave as is. What's more of an issue for me is the perennial path-searching problem when including .inp files. My observation (or just feeling?) is that when I want to include <pathprefix>/helper.inp from <pathprefix>/main.inp I either have to set the CWD to <pathprefix> or I have to give absolute, not relative paths. The first is a nuisance because I often switch projects and/or paths, the second is also not very elegant I think. I think I had questions like this already years ago which led to the CWD  being more easily settable. The recent display of the CWD in the main window also helps because it is clickable and brings up the setting dialog. But some unix-y suggestions like 'include ./helper.inp" or similar don't work on Windows (do they actually work on Linux, cannot test right now?). It would seem very natural that you could just "include" a file sitting next to you. thanks, sven