TSE: EditEnvVars.zip: Error
39 views
Skip to first unread message
knud van eeden
Jan 13, 2026, 5:28:20 PMJan 13
to SemWare TSE Pro Text Editor
Hello,
Just FYIO:
Error when compiling EditEnvVars.s in TSE for Microsoft Windows 4.50 RC24
(which is thus an example of such older editor)
with friendly greetings
Knud van Eeden
Carlo Hogeveen
Feb 1, 2026, 4:08:27 AMFeb 1
to sem...@googlegroups.com
I do not understand your point.
This is about the EditEnvVars extension, which lets us use environment variables like %TMP% in TSE’s File Open prompt.
https://ecarlo.nl/tse/ToolsAndExtensions.html#EditEnvVars
Its compatibility statement and documentation claims that it needs TSE v4.50.13 upwards.
It is therefore not expected to work in TSE 4.50 rc24, which is older.
As I often do, I even made the compiler give a nice, relevant error when someone accidentally tries to install EditEnvVars with an older TSE version.
Your information therefore seems to be that that is working.
I do not understand your point.
Carlo
--
---
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/1367191179.10806002.1768343294815%40mail.yahoo.com.
Knud van Eeden
Feb 3, 2026, 8:35:03 AMFeb 3
to sem...@googlegroups.com
FYIO:
> ---------------------------------------------------------------------------------
> 18 Jan 2021 v4.41.44
> ---------------------------------------------------------------------------------
>
> New compiler directive INTERNAL_VERSION value is that of the
> Version() function. Thanks to Carlo Hogeveen for the suggestion.
1. -Thus since v4.41.44 this 'INTERNAL_VERSION' is known.
2. -Thus 4.50 RC 13 is newer than 4.41.44 thus should know this INTERNAL_VERSION
and not cause a syntax error.
3. -But the result of running EditEnvVars.s in e.g. 4.50 RC 24 results thus a 'syntax error'.
(see in the screenshot the error line at the bottom of the screenshot: 'Error 2333 (line 67 column 3) syntax error')
In other words an error with the syntax.
Expected was e.g. not a syntax error, but a Warn() or Message() or similar.
4. -This is the culprit
#if INTERNAL_VERSION < 12420
Editor is too old. You need at least TSE v4.50.13 (27 Sep 2025).
#endif
5. And Line 67 column 3 starts thus at the begin of 'Editor is too old. You need at least TSE v4.50.13 (27 Sep 2025).'
6. -So something is wrong (syntax) with that line.
7. -Insteat trying something like using a usual IF ... ENDIF works (=compiles) also in 4.50 RC24
IF ( INTERNAL_VERSION < 12420 )
Warn( "Editor is too old. You need at least TSE v4.50.13 (27 Sep 2025)." )
ENDIF
8. -But doing some testing to get it compiled in 4.50 RC24
there are probably too many differences (e.g. new keywords) in newer 4.50.13 compared
with the older 4.50 RC24 that it will not compile at other locations anyhow.
9. -Conclusion: generating a syntax error in e.g. 4.50 RC24 is probably the best workaround
otherwise the syntax errors will always pop up at other locations in the program
anyhow and it can not compile thus.
10. -So a syntax error is kind of expected at line 67 column 3 and the best workaround.
> ---------------------------------------------------------------------------------
> 18 Jan 2021 v4.41.44
> ---------------------------------------------------------------------------------
>
> New compiler directive INTERNAL_VERSION value is that of the
> Version() function. Thanks to Carlo Hogeveen for the suggestion.
1. -Thus since v4.41.44 this 'INTERNAL_VERSION' is known.
2. -Thus 4.50 RC 13 is newer than 4.41.44 thus should know this INTERNAL_VERSION
and not cause a syntax error.
3. -But the result of running EditEnvVars.s in e.g. 4.50 RC 24 results thus a 'syntax error'.
(see in the screenshot the error line at the bottom of the screenshot: 'Error 2333 (line 67 column 3) syntax error')
In other words an error with the syntax.
Expected was e.g. not a syntax error, but a Warn() or Message() or similar.
4. -This is the culprit
#if INTERNAL_VERSION < 12420
Editor is too old. You need at least TSE v4.50.13 (27 Sep 2025).
#endif
5. And Line 67 column 3 starts thus at the begin of 'Editor is too old. You need at least TSE v4.50.13 (27 Sep 2025).'
6. -So something is wrong (syntax) with that line.
7. -Insteat trying something like using a usual IF ... ENDIF works (=compiles) also in 4.50 RC24
IF ( INTERNAL_VERSION < 12420 )
Warn( "Editor is too old. You need at least TSE v4.50.13 (27 Sep 2025)." )
ENDIF
8. -But doing some testing to get it compiled in 4.50 RC24
there are probably too many differences (e.g. new keywords) in newer 4.50.13 compared
with the older 4.50 RC24 that it will not compile at other locations anyhow.
9. -Conclusion: generating a syntax error in e.g. 4.50 RC24 is probably the best workaround
otherwise the syntax errors will always pop up at other locations in the program
anyhow and it can not compile thus.
10. -So a syntax error is kind of expected at line 67 column 3 and the best workaround.
with friendly greetings
Knud van Eeden
To view this discussion visit https://groups.google.com/d/msgid/semware/003801dc935a%245569f7a0%24003de6e0%24%40ecarlo.nl.
Knud van Eeden
Feb 3, 2026, 8:58:41 AMFeb 3
to sem...@googlegroups.com
FYIO
but with a Warn() instead.
But this at the price of added complexity by having to add #IFDEF.
So the earlier syntax error workaround is definitely the simplest.
Knud van Eeden
Feb 3, 2026, 9:01:09 AMFeb 3
to sem...@googlegroups.com
Carlo Hogeveen
Mar 1, 2026, 9:00:37 AM (11 days ago) Mar 1
to sem...@googlegroups.com
That was so much text, that at first I thought something was actually wrong, but it was just you sharing the steps of your intermediate thought-process to in the end conclude that GetEnvVars works correctly after all.
Whoop-de-doo!
Carlo
From: sem...@googlegroups.com <sem...@googlegroups.com> On Behalf Of Knud van Eeden
Sent: Tuesday, February 3, 2026 3:02 PM
To: sem...@googlegroups.com
Subject: Re: [TSE] TSE: EditEnvVars.zip: Error
On Sun, Feb 1, 2026 at 10:08 AM Carlo Hogeveen <mailto:t...@ecarlo.nl> wrote:
I do not understand your point.
This is about the EditEnvVars extension, which lets us use environment variables like %TMP% in TSE’s File Open prompt.
https://ecarlo.nl/tse/ToolsAndExtensions.html#EditEnvVars
Its compatibility statement and documentation claims that it needs TSE v4.50.13 upwards.
It is therefore not expected to work in TSE 4.50 rc24, which is older.
As I often do, I even made the compiler give a nice, relevant error when someone accidentally tries to install EditEnvVars with an older TSE version.
Your information therefore seems to be that that is working.
I do not understand your point.
Carlo
I do not understand your point.
This is about the EditEnvVars extension, which lets us use environment variables like %TMP% in TSE’s File Open prompt.
https://ecarlo.nl/tse/ToolsAndExtensions.html#EditEnvVars
Its compatibility statement and documentation claims that it needs TSE v4.50.13 upwards.
It is therefore not expected to work in TSE 4.50 rc24, which is older.
As I often do, I even made the compiler give a nice, relevant error when someone accidentally tries to install EditEnvVars with an older TSE version.
Your information therefore seems to be that that is working.
I do not understand your point.
Carlo
From: 'knud van eeden' via SemWare TSE Pro text editor <mailto:sem...@googlegroups.com>
Sent: Tuesday, January 13, 2026 11:28 PM
To: SemWare TSE Pro Text Editor <mailto:sem...@googlegroups.com>
Subject: [TSE] TSE: EditEnvVars.zip: Error
Hello,
Just FYIO:
Error when compiling EditEnvVars.s in TSE for Microsoft Windows 4.50 RC24
(which is thus an example of such older editor)
Sent: Tuesday, January 13, 2026 11:28 PM
To: SemWare TSE Pro Text Editor <mailto:sem...@googlegroups.com>
Subject: [TSE] TSE: EditEnvVars.zip: Error
Hello,
Just FYIO:
Error when compiling EditEnvVars.s in TSE for Microsoft Windows 4.50 RC24
(which is thus an example of such older editor)
with friendly greetings
Knud van Eeden
--
---
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 mailto:semware+u...@googlegroups.com.
Knud van Eeden
--
---
You received this message because you are subscribed to the Google Groups "SemWare TSE Pro text editor" group.
To view this discussion visit https://groups.google.com/d/msgid/semware/1367191179.10806002.1768343294815%40mail.yahoo.com?utm_medium=email&utm_source=footer.
--
---
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 mailto:semware+u...@googlegroups.com.
---
You received this message because you are subscribed to the Google Groups "SemWare TSE Pro text editor" group.
To view this discussion visit https://groups.google.com/d/msgid/semware/003801dc935a%245569f7a0%24003de6e0%24%40ecarlo.nl?utm_medium=email&utm_source=footer.
--
---
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 mailto:semware+u...@googlegroups.com.
---
You received this message because you are subscribed to the Google Groups "SemWare TSE Pro text editor" group.
To view this discussion visit https://groups.google.com/d/msgid/semware/CANo7bXRVry%2BnTZpLi6uzy5%3D8915PkV_vXOihW-zUWDGZDcOkjA%40mail.gmail.com?utm_medium=email&utm_source=footer.
Knud van Eeden
Mar 1, 2026, 1:13:07 PM (11 days ago) Mar 1
to sem...@googlegroups.com
it was thus just FYIO.
with friendly greetings
Knud van Eeden
Artificial Intelligence
IT specialist
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/032901dca983%24c858b960%24590a2c20%24%40ecarlo.nl.
Claus Futtrup
Mar 1, 2026, 1:33:13 PM (11 days ago) Mar 1
to sem...@googlegroups.com
Just my two cents.
Knud deserves positive feedback for putting it all into one email and
not many ...
With kind regards,
Claus
Reply all
Reply to author
Forward
0 new messages