QShell GOTCHA -- MIDRANGE-L

Subject: QShell GOTCHA
From: "James H. H. Lampert" <jamesl@xxxxxxxxxxxxxxxxx>
Date: Fri, 01 Dec 2017 10:57:16 -0800
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

I just discovered something about QShell:

It seems that "echo" and "ECHO" are two different commands, that behave slightly differently:

"echo" resolves standard C/Java/*nix escapes. "ECHO" does not.

Also, if you do "help echo," you get the syntax. If you do "help ECHO," you get nothing.

To illustrate:

help echo
echo: echo [argument ...]
$
echo "foobar\r"
foobar
$
help ECHO
help: 001-0014 Command ECHO not found.
$
ECHO "foobar\r"
foobar\r
$

Would anybody happen to know what's up with this apparently undocumented insanity?

--
JHHL

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: QShell GOTCHA , David Gibbs
Re: QShell GOTCHA , Nathan Andelin

This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.