Am 07.11.2022 um 18:18 schrieb Summers, Peter: > Hi all, > > FWIW on Windows 10 Enterprise with Gretl 2022c, "pkg install DP.gfn" works > fine from the console, as does "include DP.gfn". But I'm also not seeing it > in my local listing. Thanks for checking, Peter. When I restart gretl, first I don't get a crash on entering "pkg install DP.gfn", either. However, when I have both the local package listing window and the window with the server listing open, then typing the command leads to a reproducible crash.

Am 08.11.2022 um 13:59 schrieb Allin Cottrell: > On Tue, 8 Nov 2022, Sven Schreiber wrote: > >> Am 07.11.2022 um 18:18 schrieb Summers, Peter: >>> Hi all, >>> >>> FWIW on Windows 10 Enterprise with Gretl 2022c, "pkg install DP.gfn" >>> works fine from the console, as does "include DP.gfn". But I'm also >>> not seeing it in my local listing. >> >> Thanks for checking, Peter. When I restart gretl, first I don't get a >> crash on entering "pkg install DP.gfn", either. However, when I have >> both the local package listing window and the window with the server >> listing open, then typing the command leads to a reproducible crash. > > Ah, I can reproduce that here. It's now fixed in git. The problem was > specific to having the server listing window open when issuing the > "pkg install" command. There was an error in the code that scanned the > server window to update the status string for the package in question > to make it say "Up to date". > Thanks, Allin - is that also supposed to fix the DP-not-showing-up issue that Peter and I have been seeing?

On Tue, Nov 8, 2022 at 11:31 AM Cottrell, Allin <cottrell(a)wfu.edu&gt; wrote: > I doubt it. I'm planning to produce a debugging build for Windows > which should expose whatever is blocking DP's appearance in the local > listing window. That's now available at http://users.wfu.edu/cottrell/gretl/gretl_install-64.exe You need to run gretl.exe with the --debug flag, as described in section 50.1 of the User's Guide. Then you'll get a console window showing what gretl writes to stderr.

Am 08.11.2022 um 17:45 schrieb Cottrell, Allin: > > You need to run gretl.exe with the --debug flag, as described in > section 50.1 of the User's Guide. Then you'll get a console window > showing what gretl writes to stderr. OK, I think we're getting there, here's what gretl is claiming when the listing window is opened: duplicated function package: DP.gfn 1.3 C:\Users\<...>\AppData\Roaming\gretl\functions\DPB [first instance found] C:\Users\<...>\AppData\Roaming\gretl\functions [duplicate] I had already quietly speculated whether DP and DPB would be too similar as names, but I found the idea quite far-fetched because I thought a machine/software wouldn't care as long as the names aren't exactly identical (up to lower vs. upper casing)...