I have found this a nuisance in the past, sometimes revealing passwords to
users on net use commands.  Glad to see it go!

Jon

<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Virus-free.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Sat, 27 Apr 2019 at 19:59, Erich Steinböck <erich.steinbo...@gmail.com>
wrote:

> On Windows, our default command handler changes the console window title
> to "path-to-cmd\cmd.exe /c executing-command" and after the command
> finishes, reverts it to what it was before.
>
> Is there a good reason we're doing this? Windows batch files don't do it,
> and most commands won't run long enough for a user to actually be able to
> read the new title.
>
> I intend to make the new SYSTEM and PATH command environments skip this
> title change.
>
> Do we want to keep the console title changing for commands running in our
> existing environments CMD and "" ?
> _______________________________________________
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Reply via email to