Surely that can be addressed by adjustments to the PATH environmental variable.
Sent by Magic!
> On Dec 7, 2016, at 12:47 PM, Terry Fuller wrote:
>
> The replacement for cmd.exe is powershell. It's already available in
> several releases, alongside cmd.exe. It is, however
The article say that going forward, cmd.exe will no longer be distributed. The
power shell provides all the functionality that cmd.exe has in the past.
This is somewhat like UNIX/Linux which replaced the Bourne Shell (sh) with the
Bourne Again Shell (bash) many years ago.
Bruce
Sent by
The replacement for cmd.exe is powershell. It's already available in
several releases, alongside cmd.exe. It is, however not backward
compatible... things like invoking a program from the current directory
in powershell requires .\pgm.rex rather than pgm.rex. Several other
non-compatible
I agree with Mark's reading. That environment is not going away, but will
no longer be the default. It would be nice if ooRexx had a powershell
address environment. Not sure who has the interest in implementing one
though.
Rick
On Wed, Dec 7, 2016 at 2:56 PM, Mark L. Gaubatz
The article is highly misleading. If I am reading the sources properly,
MS is completing the deprecation of the MS-DOS command line environment
in favor of PowerShell. The CW article absolutely did the environment a
disservice in their presentation.
Mark
On 12/07/2016 11:32 AM, Michael Lueck
The article is highly misleading. If I am reading the sources properly,
MS is completing the deprecation of the MS-DOS command line environment
in favor of PowerShell. The CW article absolutely did the environment a
disservice in their presentation.
Mark
On 12/07/2016 11:32 AM, Michael Lueck
Michael, ooRexx will run fine in a PowerShell window as long as the COMSPEC
environment variable points to a program that will execute host commands.
If CMD.EXE really were to disappear, ooRexx could still issue any host
command, which the program COMSPEC points to, is able to run.
On Wed, Dec
Greetings Rony,
Rony G. Flatscher wrote:
> what are your sources?
"Say goodbye to the MS-DOS command prompt"
http://www.computerworld.com/article/3147668/operating-systems/say-goodbye-to-the-ms-dos-command-prompt.html
> If MS would remove cmd.exe most programs (including their owns) would
Michael Lueck wrote:
> However for legacy support, I do end up touching Windows frequently. ;-)
> Valid question still stands. I am thankful,
Last I checked OORexx runs in Cygwin xterms. Are those broken in Windows 10?
--
Jack Woehr # "Democracy is the theory that the common
Michael,
what are your sources?
If MS would remove cmd.exe most programs (including their owns) would break.
Therefore it is very
unlikely that they remove cmd.exe support.
---rony
On 07.12.2016 19:02, Michael Lueck wrote:
> Greetings Team,
>
> I recently read of Microsoft's plan to remove
Jack Woehr wrote:
> Michael Lueck wrote:
>> I would think ooRexx would need some sort of replacement of cmd.exe to send
>> shell commands to.
>
> The replacement is readily available. It's called "Linux" :)
I know that... I have been using Linux as my primary desktop OS since 2007.
However for
Michael Lueck wrote:
> I would think ooRexx would need some sort of replacement of cmd.exe to send
> shell commands to.
The replacement is readily available. It's called "Linux" :)
--
Jack Woehr # "Democracy is the theory that the common people
Box 51, Golden CO 80402 # know
Greetings Team,
I recently read of Microsoft's plan to remove cmd.exe from a coming update to
Windows 10. What impact will that removal have on ooRexx?
Is the ability to run a text mode application also under attack, or for now
just removal of cmd.exe?
I would think ooRexx would need some
13 matches
Mail list logo