QB64 odd behavior when Windows Terminal is set to default terminal app

[bert22306]

Simple way to think of the differences in the two:

SHELL "cmd /c qb65pe.exe"
SHELL "powershell -run qb64pe.exe"

Two different terminals launching the program, and with different interfaces for each.  Similar, but distinct in the closing behavior.  Console will run and close, Terminal will run and wait for execution to finish, then close.

Okay, so how does this react to the PowerShell settings fof Terminal:

$Console:Only
_Dest _Console
$ScreenHide

I use this in quite a few QB64pe programs, when it's helpful to be able to scroll way back.

And, how would you run .bat or .cmd scripts? When I tried, they did not work.

[SMcNeill]

Okay, so how does this react to the PowerShell settings fof Terminal:

$Console:Only
_Dest _Console
$ScreenHide

I just checked to make certain I wouldn't tell you something wrong. 

The above will open the TERMINAL (if that's your default setting), and since it's $CONSOLE:ONLY, it uses the existing terminal which appears at startup. 

You don't have it make a terminal, then start QB64PE, then QB64PE start a second terminal.

It simply opens the terminal and then assigns that window to QB64 for input/output.

And, how would you run .bat or .cmd scripts? When I tried, they did not work.

SHELL "cmd /c my_bat.bat"    <-- The easiest way.  Specify that you're shelling to a command window and not a terminal.  That's really all there is to it, but if you expect to keep using that .bat file in the future, you might want to look into what it'd take to swap over to powershell type commands and make it a *.ps script instead.

I really do think that someday down the road (and it may not be for 10 years from now, but *someday*), Windows will drop Console completely.  wmic is gone already.  Other tools are slowly being depreciated that people don't notice... until they do.  I imagine they'll go they same path the did with Explorer and Edge:

Explorer is in all OSes.
Explorer and Edge are both on the OS.
Edge is on the OS and Explorer becomes a download feature.
Edge is standard and Explorer is no longer supported.

The Terminal/Console thing seems to be following the same path of implementation.

[Kernelpanic]

The whole thing seems to be organized quite differently under Win 11 than under Win 10. I have also installed the Terminal alongside Powershell, but I haven't encountered any of the problems described.

[bert22306]

Thanks, Steve! I'll save your post and try everything out.