TSE: Linux: Microsoft: Windows: Linux: How to possibly make the TSE for Linux version as equal as possible to the TSE for Microsoft Windows version

[knud van eeden]

Hello,

FYI

1. Using TSE for Linux 4.50.14 (because that has thus system clipboard functionality which is very important).

2. For the moment my TSE for Linux version has been made as equal as possible to the TSE for Microsoft Windows version.

3. Using an almost equal configuration file in TSE for Linux versus the configuration file for TSES for Microsoft Windows.

(TSE menu 'Write settings to ASCII file' in both, doing a 'diff', making equal, saving then burning using ./sc32 -b yourfilename.cfg

That gives e.g. equal colors and other equal behavior in both).

4. Added the menu options (8 totally: FileMenu, TextMenu, ..., HelpMenu) from my Microsoft Windows version

and added those to the TSE for Linux .ui (e.g. tse.ui)

Using the conditional compilation method I can e.g. easy switch between old menus and new menus.

Then burn again that .ui (I have my extra .ui configurations in 2 separate files, before and after, and compile using #include

and burn it using ./sc32 -b <youruiconfigurationfile>

5. I burned all the keyassignments from my TSE for Microsoft Windows into TSE for Linux.

I can do that quite easily because I have the key assignments separated, when compiling

I use #include to collect all the different parts which make up my .ui (e.g. tse.ui).

A bit of editing and thus using #include to collect the partial files).

6. Then in the course of time changing some of my TSE macros which do not run in TSE for Linux yet.

Typically using WhichOS(), _LINUX_, _WINDOWS_, _WINDOWS_NT_. 

Less conditional compilation #IFDEF #ELSE #ENDIF.

7. If I now get to resolve the maximize screen issue ('menu too large') with large TSE menus (something like 1500 menus here) then already very far

in making both almost behaving equally (e.g. using the same key combinations or equal menu options in both which is handy if

blind typing). That is expected to be resolved in TSE for Linux version 4.50.16 thus.

with friendly greetings

Knud van Eeden

[knud van eeden]

LATEST UPDATE 9 December 2025:

Hello,

FYI

 For the moment my TSE for Linux version has been made as equal as

 possible to the TSE for Microsoft Windows version.

 This by using as much as possible:

  Note: Keeping it as much as possible the same means that one can use his typing 

        and options to chose habits

        unchanged in all environments, so having to change

        less already long time used behavior and having to remember less and being

        abloe to do things more easily and automatically without

        having to think and analyze too much all the time.

  Note: Semware has already by design applied that principle of keeping

        the system running on Linux or Microsoft Windows as much as

        possible the same (e.g. same filenames (e.g. in the 'mac'

        directory), same .ui files (e.g. in the .ui directory), ...)

  1. Same system clipboard options

      Using TSE for Linux version 4.50.14 (or higher when available)

      (because that has thus system clipboard functionality which is

      very important, because one can very easily exchange text

      information via the system clipboard (<Ctrl c>, <Ctr v>, <Ctrl x>,

      further <Ctrl z>, <Ctrl y>) between a TSE for Linux and TSE

      for Microsoft Windows now.

  2. Same configuration .cfg file

      Using an almost equal configuration file in TSE for Linux versus

      the configuration file for TSES for Microsoft Windows. (TSE menu

      'Write settings to ASCII file' in both, doing a 'diff', making

      equal, saving then burning using ./sc32 -b yourfilename.cfg That

      gives e.g. equal colors and other equal behavior in both).

      Also selecting the more general, generic options instead

      of specialized options.

  3. Same menu options in the tse.ui

      Added the menu options (8 totally: FileMenu, TextMenu, ...,

      HelpMenu) from my working Microsoft Windows version (currently

      4.50 RC24) and added those to the TSE for Linux .ui (e.g. tse.ui)

      Using the conditional compilation method I can e.g. easy switch

      between old menus and new menus. Then burn again that .ui (I have

      my extra .ui configurations in 2 separate files, before and

      after, and compile using #include and burn it using ./sc32 -b

      <youruiconfigurationfile>

  4. Same key assignments in the tse.ui

      I burned all the keyassignments from my TSE for Microsoft Windows

      into TSE for Linux. I can do that quite easily because I have the

      key assignments separated, when compiling I use #include to

      collect all the different parts which make up my .ui (e.g.

      tse.ui). A bit of editing and thus using #include to collect the

      partial files).

  5. Same TSE macro filenames to run the same in all the environments

      Then in the course of time changing some of my TSE macros which do

      not run in TSE for Linux yet. Typically using WhichOS(), _LINUX_,

      _WINDOWS_, _WINDOWS_NT_ because that is a more generic solution.

      Less conditional compilation #IFDEF #ELSE #ENDIF.

       1. -Microsoft Windows

       2. -Linux WSL

       3. -Linux non-WSL

  6. Same filename as input (e.g. c:\temp\foobar.s)

      Getting the correct filename as output

       Output the correct prefix for a filename depending on running that

       same TSE macro program in:

        1. -Microsoft Windows (e.g. c:\temp\foobar.s)

        2. -Linux WSL (e.g. /mnt/c/temp/foobar.s)

        3. -Linux non-WSL (e.g. /home/username/temp/foobar.s)

  7. Same external .ini file

      Using all the same external .ini file with its parameter values

      while you are running in:

       1. -Microsoft Windows

       2. -Linux WSL

       3. -Linux non-WSL

  8. Same mouse options available

      Only the mouse options are still not fully available. That might

      require further changes in the TSE source code, e.g. the terminal

      escape codes methods used:

       1. X10 (older restricted mouse encoding currently used in TSE SAL)

       2. SGR (newer less restricted mouse encoding currently not used in TSE SAL. To be implemented instesad)

  9. Same workarounds or solutions

      E.g. 'Menu too large' error (workaround via maximizing the screen first)