Does not work well: rlwrap + rxvt + cmd

Ronald Fischer
Thu Aug 25 07:51:00 GMT 2011

On Wed, 24 Aug 2011 11:56 -0400, "Eliot Moss" <> wrote:
> On 8/24/2011 11:52 AM, Ronald of Steiermark wrote:
> > On Wed, 24 Aug 2011 08:39 -0700, "Andrew DeFaria"<>
> > wrote:
> > For instance, to test the cruel BAT files which we are going to deliver.
> You can run .bat files from bash and other Cygwin shells.

You can *run* them, but the effect is not always the same. 

For example, setting an environment variable within a batch file under
CMD.EXE results in the environment variable being visible in the calling
environment (similar to "sourcing" a file in bash), while calling the
batch file from bash leaves the environment intact. 

Also, some internal commands (for example COPY) are not present in bash,
though this can be easily remedied using an alias or a shell function.

Other problems are related to the use of \ as a path separator. Imagine
that some of your BATCH files generate environment variables containing
a Windows path, 
and simply because bash command lines are interpreted differently than
Windows CMD command line (for example, when it comes to quoting or
parameter substitution).

The main problem, however, is: If you are going to deliver something,
which is supposed to run under CMD.EXE,  most customers won't accept it
until you really have tested it under CMD.EXE, and for good reason. In
fact, even though I got running rxvt with cmd thanks to all the
suggestions to my post, I will do some *final* tests  still in plain,
native Windoze Command-Windows, just for the safe side.

Using a bash shell as a "main work horse" is great, but when you have
the pleasure to create and test batch files, you will sooner or later be
happy to also have a CMD shell available...

> In both cases you generally to present Windows paths, of course;
> cygpath can help with that.

I use cygpath in several of my scripts and it's extremely useful, but
dealing with the various path representations in interactive work is,
for me at least, an annoyance...

Thank you for your suggestions, though!

Ronald Fischer <>
+  If a packet hits a pocket on a socket on a port, 
+  and the bus is interrupted and the interrupt's not caught,
+  then the socket packet pocket has an error to report.
+		(cited after Peter van der Linden)

Problem reports:
Unsubscribe info:

More information about the Cygwin mailing list