[Hugs-bugs] Re: [Hugs-users] Setting Search Path doesn't persist in WinHugs

[Sigbjorn Finne]

Hi,

odd, I'm unable to reproduce this here -- path settings are persisted
OK in the Registry (this is with an account that lacks Admin
privs), and I'm able to see them when restarting. There's three
reasons why the default search path settings will be used:

   - the -P setting makes the Prelude module invisible; the interpreter
     issues a warning when this happens.
   - an empty -P setting is used to reset the path upon startup.
   - the environment variable IGNORE_USER_REGISTRY
      is set.

What WinHugs version are you using?

--sigbjorn

----- Original Message ----- 
From: "Greg Ballinger" <gregb at netrox.net>
To: <hugs-users at haskell.org>
Sent: Friday, April 23, 2004 23:15
Subject: [Hugs-users] Setting Search Path doesn't persist in WinHugs


> I've made many attempts to add a directory to the search path using
:set -P
> using different strings such as
>   -P: {Home}/Haskell  and
> -P;"C:\Documents and Settings\Greg\My Documents\Haskell"
>
> All have worked during the current WInHugs session (Yes, I created the
Home
> environment variable). When I look in the HKEY-CURRENT-USER registry, the
> information is saved in the option string:
> -s -t -g -G -l -. +q -Q -w -k -o -O +u -I -T -A +R -H +98 -h250000 -p"%s>
"
> -r"$$"
> -P".:{Hugs}/libraries:{Hugs}/oldlib:{Hugs}/libraries/win32:{Home}/Haskell"
> -S".hs;.lhs" -E"C:\\Program Files\\UltraEdit\\UEDIT32.EXE" -c40
>
> However, when I quit and restart WinHugs it only loads the default search
path
>   : -P.:{Hugs}/libraries:{Hugs}/oldlib:{Hugs}/libraries/win32
>
> At this point I need to update the search path every time I start WinHugs.
> Does anyone have a helpful suggestion? I noticed some discussion back in
> 2001 about how easy/dangerous it was to change the registry but apparently
> nothing related to my  particular issue. By the way my editor setting
> persists with no problem.
>
> On a possibly related note, the documentation states that the installer
> sets options in the HKEY-LOCAL-MACHINE but when I checked those registry
> entries all I found were placeholders with no values set.
>
> Thank you for your assistance!
>
> --Greg Ballinger
>