|
From: Elliott S. <ell...@gm...> - 2011-04-11 04:37:37
|
2011/4/10 Anton Vodonosov <avo...@ya...>
>
> 10.04.2011, 23:33, "Elliott Slaughter" <ell...@gm...>:
> >
> > Anton: Did you install this "for everyone" or "just for me"? Have you
> ever had any previous versions of CLISP installed via the installer on this
> machine?
> >
> >> Elliott, could you please take a look at
> clisp/win32msvc/nsis/add_to_path.nsh?
>
> "for everyone". Previously I had installed CLISP 2.48, which I uninstalled
> manually from control panel before installing the new installer.
>
> I can not say what mode (everyone/just for me) was use in the old, 2.48,
> installation.
>
I can't seem to reproduce the bug you observed. I also had CLISP 2.48
installed ("just for me") before starting, uninstalled it, and then
installed CLISP 2.49 ("for everyone"). At every step my user and system
PATHs were still intact, and CLISP path got added and removed as expected. I
am also using Windows 7 64-bit, so no difference there.
I'm not exactly sure what to do from here if I can't reproduce the bug...
In the meantime I do have a patch for the other issue I found (regarding the
start menu), but I'll start another thread for that.
--
Elliott Slaughter
"Don't worry about what anybody else is going to do. The best way to predict
the future is to invent it." - Alan Kay
|