The Real 4.50.15 is here

[S.E. Mitchell]

Get it here:
https://semware.com/files/tse-pro-install/tse-setup-4.50.15.zip

-------------------------------------------------------------
06 Dec 2025 v4.50.15
-------------------------------------------------------------
Lots of additions/changes to sanity1 macro.
If you get a chance, run it to see if all tests pass.

In all .ui files, the following added:
<Shift Del> CutToWinClip()
<Ctrl Ins> CopyToWinClip()
<Shift Ins> PasteFromWinClip()
Thanks to Knud van Eeden for the suggestion.

In tse.ui and ws.ui, these are what shows on the menus.
For the win.ui, it shows the Windows standard keys,
<ctrl x>, <ctrl v>, <ctrl c>

Fixed a bug in StrFind() vs. MarkFoundText(), where
MarkFoundText() did not always work. Test case added to sanity.
Thanks to Carlo Hogeveen for the report.

I introduced a bug into the Dos() and lDos() commands. When
calling the same such that they use the command processor, I
added the "/d /q" switches, which makes the command processor
start somewhat quicker. However, in the process, I broke those
commands, which caused Carlo's uncrash and the compile macro to
fail. This has been fixed. Thanks to Carlo Hogeveen for the
report.

Reset the editor color palette to the Windows 7 console colors,
which is what the editor has used for years. Thanks to Carlo
Hogeveen for the suggestion.

Editor font problems - thanks to Carlo Hogveen for the detailed
report:

To set Windows 11 Pro's code page to/from 65001, go to Setings
-> Time & language -> Language & region -> the most-right
down-symbol besides "Display Language", and turn "Beta: Use
Unicode UTF-8 for worldwide language support" On or Off.
In my experience afterwards you need to restart Windows 11 Pro
too for consistent results.
In Windows 10 the option is under Settings -> Time & Language
-> Language -> (In top right:) Administrative language settings
-> Change system locale.

To reproduce GUI TSE's inconsistency:
The Windows UTF-8 option is set to On and Windows was restarted
afterwards.
In a new TSE installation where the font's properties were
never changed:
- The font is NOT Terminal.
- TSE's ASCII Chart menu does not show real characters from
character 128 upwards.

1. If you open TSE's font menu and select OK, then TSE's ASCCII
Chart menu gains proper characters for the upper 128 ones.

2. If you Macro Execute (including the "execute"!) execute
string fn[255]='' integer fs=0 integer ff=0 GetFont(fn, fs, ff)
SetFont(fn, fs, ff) then the ASCII Chart menu loses proper
characters for the upper 128 ones. (I see open block
characters.)

Both these changes can be made persistent across TSE sessions
by saving TSE's settings.

Here is the problem / bug: As the second change suggests, it is
not possible to use the SetFont() function in GUI TSE with a
not-Terminal font if the external code page is 65001, because
that makes GUI TSE lose its upper 128 characters.
This can also not be repaired or worked around by a macro.
Normally GUI TSE (without the Terminal font) internally uses
code page 1252 whatever the external code page is, but for
external code 65001 that fails.

This has been fixed.

When using non-OEM fonts, the menu to the left of [File] was not
showing. This was fixed.

SearchPath() updated to only search the system PATH if both path
and dir are not passed or both are passed as "".

In some instances, pasting from the Windows clipboard or
inserting a file could add an extra line. This was introduced
when adding Linux clipboard processing. This has been fixed, and
test cases added to sanity.

Bug in sc: Following macro crashes sc32:

<f3> if 1
return ()
endif

Fixed.

The View Finds Load Files command was broken (maybe since 2022).
It would not load all the files listed. This has been fixed.

-------------------------------------------------------------

[Knud van Eeden]

Hello Sammy,

Still the error it seems:

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 semware+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/semware/CA%2BgEvka_Z7g%3DJACN8ackn1oEZEBUEH1_fMa6Nr81-FD131xRxA%40mail.gmail.com.

[Knud van Eeden]

[S.E. Mitchell]

Load a .s file.

Can you select Macro, Compile Menu.

Select Debug Compiler Setup.

And see if you see anything fishy.

Thanks in advance!

To view this discussion visit https://groups.google.com/d/msgid/semware/CANo7bXQ-d9mtcGwnTw7b%2BNsW%2Brsd8Utru71FnAnhtOfTy7JpmQ%40mail.gmail.com.

[Knud van Eeden]

OK, testing...

To view this discussion visit https://groups.google.com/d/msgid/semware/CA%2BgEvkap%3DqEMhD%3DLrR3XXBooe8C1Xx5hk7_tsrqp2eZVnPV6xw%40mail.gmail.com.

[Knud van Eeden]

Following the steps, stuck almost immediately at step 2.

[Knud van Eeden]

And the sc32.exe is for sure in the TSE main directory present:

[S.E. Mitchell]

Found the problem.  In the compile macro.

Fix coming soon.

To view this discussion visit https://groups.google.com/d/msgid/semware/CANo7bXSeZdDx3gwkawrHOkAL9wZuORA3E%3DtvMvfATZpwkmpgwA%40mail.gmail.com.

[Knud van Eeden]

And there is NO difference between the 'Write settings to ASCII file' .cfg file for the 

4.50.13 (that does NOT have that compiler issue)

and

4.50.15 (that does have that compiler issue).

So the root cause MUST be INTERNAL to g32.exe source code.

[S.E. Mitchell]

There is a new compile.s at:
https://semware.com/files/tse-pro-install/compile.s
That fixes the problem.

On Sat, Dec 6, 2025 at 3:54 PM Knud van Eeden <knud.va...@gmail.com> wrote:
>
> And there is NO difference between the 'Write settings to ASCII file' .cfg file for the
>
> 4.50.13 (that does NOT have that compiler issue)
>
> and
>
> 4.50.15 (that does have that compiler issue).
>
> So the root cause MUST be INTERNAL to g32.exe source code.
>
>
>

> On Sat, Dec 6, 2025 at 9:46 PM Knud van Eeden <knud.va...@gmail.com> wrote:
>>
>> And the sc32.exe is for sure in the TSE main directory present:
>>
>>
>>

>> On Sat, Dec 6, 2025 at 9:45 PM Knud van Eeden <knud.va...@gmail.com> wrote:
>>>
>>>
>>> Following the steps, stuck almost immediately at step 2.
>>>
>>>
>>>
>>>

>>> On Sat, Dec 6, 2025 at 9:42 PM Knud van Eeden <knud.va...@gmail.com> wrote:
>>>>
>>>> OK, testing...
>>>>
>>>>
>>>> On Sat, Dec 6, 2025 at 9:25 PM S.E. Mitchell <sammy.m...@gmail.com> wrote:
>>>>>
>>>>> Load a .s file.
>>>>> Can you select Macro, Compile Menu.
>>>>> Select Debug Compiler Setup.
>>>>> And see if you see anything fishy.
>>>>> Thanks in advance!
>>>>>
>>>>>
>>>>>
>>>>> On Sat, Dec 6, 2025 at 3:15 PM Knud van Eeden <knud.va...@gmail.com> wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Sat, Dec 6, 2025 at 9:14 PM Knud van Eeden <knud.va...@gmail.com> wrote:
>>>>>>>
>>>>>>> Hello Sammy,
>>>>>>>
>>>>>>> Still the error it seems:
>>>>>>>
>>>>>>> with friendly greetings
>>>>>>> Knud van Eeden
>>>>>>>
>>>>>>>
>>>>>>>

> To view this discussion visit https://groups.google.com/d/msgid/semware/CANo7bXRSLUW_D_pJWmAQ%3DP_q4Kws3tfi26%3DE27FpaqkubXH_jw%40mail.gmail.com.

[Knud van Eeden]

Yes, resolves the compiler issue.

1. Download that .s

2. Put it in your TSE 4.50.15 mac directory (overwrite or backup the old compile.s first optionally)

3. Recompile it using 4.50.15 sc32.exe, so you get a new compile.mac file there.

4. Then compiling from within the TSE editor works.

     

    

To view this discussion visit https://groups.google.com/d/msgid/semware/CA%2BgEvkZZCCVWpoNkAnwza1rpJgDsjPnrVGu_BzgLkfpywMpk%2Bg%40mail.gmail.com.

[S.E. Mitchell]

FYI: I have updated the .zip to include the new compile.s.

--

To view this discussion visit https://groups.google.com/d/msgid/semware/CANo7bXQWkxCYW7TL8pmYwdHMwoPPoKyoWyDOB4vH94cJsXgUVQ%40mail.gmail.com.