Macro language CodePage suggestion

[Carlo Hogeveen]

This regards a minuscule issue, that in practice has not blocked anything yet.

Suggestion:
In all contexts TSE's internal CodePage variable initially returns Windows' global code page (as opposed to a command prompt's local
code page).
This should be a read-only variable, because unfortunately a macro can Set(CodePage, <other value>), which has no effect whatsoever,
other than robbing other macros from a convenient way of finding out what Windows' global code page is.

There are precedents.
A macro trying to Set(WindowCols, <some value>) receives a compiler error.

Carlo

[S.E. Mitchell]

This is done - it was a simple configuration change.
--
Sammy Mitchell

> --
>
> ---
> You received this message because you are subscribed to the Google Groups "SemWare TSE Pro text editor" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to semware+u...@googlegroups.com.
> To view this discussion visit https://groups.google.com/d/msgid/semware/001501db89f7%24aec44f70%240c4cee50%24%40ecarlo.nl.