Hello Lee Peedin,
> Windows 10 has a "fresh command prompt and lots of hotkeys
.
.
.
> Again, go the the properties of the command prompt window under
Experimental and try turning "off" using Ctrl-C / Ctrl-V for copy/paste
First thank you for the education on Windows 10 and changes to the Command
Prompt. Two thoughts:
1) How does this change ooRexx for Windows in both the documentation,
the product (itself), and the ooRexx code we've all written . Some of the
code won't have any issues with Windows 10 and other might have some
issues. I know the program (console and GUI) I wrote to interface with
Window's Power routines didn't work "out of the box," but didn't take much
rework. I'm just glad its for me and I don't need to worry about
supporting both 7 and 10.
2) The final / retail version doesn't have anything (I could find)
called experimental under properties. If it is there, I'd appreciate help
in finding it. I did find Properties -> Options -> Edit Options -> check
box for "Enable Ctrl key shortcuts."
The article you point us to, though, has many more key combinations than
just Ctrl key shortcuts. Thus I'm not sure where the past and present come
together.
===> You're right, though, UNCHECKING the "Enable Ctrl key shortcuts"
returns Ctrl C back for Command Prompts NOT started by an ooRexx program.
The problem I reported on Windows 7 where Command Prompts started by an
ooRexx Program can't use Ctrl C to break/terminate anything still exists.
An example is:
1) I had an ooRexx program start a command prompt. For example:
start "Command Prompt" /D "%HOMEDRIVE%%HOMEPATH%" /MIN
"C:\Windows\system32\cmd.exe" /K "c:\autoexec.bat"
2) Insured there was NO check in the box for "Enable Ctrl key shortcuts."
3) In the new command window, I issued the command "dir \ /s" and after
it started did a "Ctrl C." The dir command kept going and going.
4) I tried just doing Ctrl-C at the command line and got a double blank
line between prompts. (On a command windows started without ooRexx, you
get the next prompt immediately following the current prompt.)
I realize with the dir command you can use Ctrl-Break to terminate the dir
command, but this doesn't work for all commands. An example is the PING
command. Ctrl-Break and ping gives summary results, while Ctrl-Break
terminates the ping command.
>From what I can tell the issues with Ctrl-Break are all the same as the
ticket I opened with ooRexx and Windows 7. What is new for the developers,
though, is how Windows 10 changes will affect ooRexx.
I do hope they will find both the time and technical expertise to address
these issues and thus keep ooRexx the outstanding product it is for Windows
users.
Thank you,
Bertram Moshier
+========================================================+
||
||
|| What I would love to do is run (legally) VM/ESA at home on my PC at a
price ||
|| a guy on SSDI can afford. Not as or for a business, but for the fun of
it. ||
||
||
+=========================================================+
------------------------------------------------------------------------------
_______________________________________________
Oorexx-users mailing list
Oorexx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-users
