#274 Windows installer should add .rxs to PATHEXT

None
open
nobody
5
2012-08-22
2008-05-28
Anonymous
No

The installer for Windows adds the ;.REX entry to the Environment variable PATHEXT.

The .REX extention is connected with the rexx.exe interpreter.

The installer for Windows does NOT add the ;.RXS entry to the Environment variable PATHEXT.

The .RXS entention is connected with the Microsoft Windows Scripting Host.

The installed should add the ;.RXS entry to the PATHEXT. (Like Microsoft does for ;.VBS;.VBE;.JS;.JSE;.WSF;.WSH)

Discussion

  • Mark Miesfeld

    Mark Miesfeld - 2008-06-01

    Logged In: YES
    user_id=191588
    Originator: NO

    I'm not 100% sure that .rxs should be added to PATHEXT. We certainly could add it.

    Adding an extension to PATHEXT is simple to do. I personally am more in favor of documenting how to do it better in the WSH part of the documentation and letting the user decided if they want it or not.

    On the other hand, I do believe adding .rex to PATHEXT and setting up the file association for the interprete adds value, so maybe this is in the same category.

    If you really think this should be done, generate some discussion on it either on the developer's list, or the RexxLA list. If there is support for doing it, it's a relatively easy thing to do.

     
  • Mark Miesfeld

    Mark Miesfeld - 2009-07-02

    This is not a bug, as the Windows installer was working as designed. It was not intended to add .rxs to PATHEXT.

    At first I wasn't sure this was a good thing to do. But, it is actually a reasonable request. And, I'll probably implement it.

    So, I'm changing this to a feature request and indicating it will probably be accepted.

     


Anonymous

Cancel  Add attachments





Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks