#178 VMS language mode inconsistencies

[Chris Ross]

The VMS NEdit 5.3 default for the PostScript language
mode is:
PostScript:.ps .PS .eps .EPS .epsf
.epsi:\"^%!\":::::\"/%(){}[]<>\"

While the VMS updatePatternsTo5dot3 function updates
it to:
PostScript:.ps .PS .eps .EPS .epsf .EPSF .epsi
.EPSI:\"^%!\":::::\"/%(){}[]<>\"

These should probably be consistent. The next release
may need to check for either of these patterns, and
update it to the correct one.

If VMS is case-sensitive, other VMS language modes
need both upper- and lower-case filename extensions.
Otherwise, the VMS language mode filename extensions
should be all-upper-case copies of the originals, as
in the Python language mode. So, VMS PostScript would
be:

PostScript:.PS .EPS .EPSF
.EPSI:\"^%!\":::::\"/%(){}[]<>\"

[Thorsten Haude]

Logged In: YES
user_id=119143

I think this should be done when the next release is prepared.

[Thorsten Haude]

Logged In: YES
user_id=119143

Also see discussion in the mailing list starting here:
http://www.nedit.org/pipermail/develop/2006-August/012085.html

[Tony Balinski]

Logged In: YES
user_id=618141
Originator: NO

Curiously case-independent matching for VMS is handled in preferences.c for VMS versions greater than 7.2, so we shouldn't need to have upper and lower case versions of each extension for VMS. Why we need the VMS version is beyond me: earlier versions may save the name in uppercase only, but the OS lets you identify in either upper or lower case. MS Windows is similar and should be treated accordingly.

On another note, the number of extensions you can specify is limited to 20. It's easy to remove the restriction.

[Thorsten Haude]

Logged In: YES
user_id=119143
Originator: NO

Seems to be very easy to do, but nobody cares, so reprio.