Re: QShell GOTCHA

FYI even the ancient, depreciated, yet ever present SEU has the ability to let you change the default case to lower. :-)

- Larry "DrFranken" Bolhuis

www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.

On 12/1/2017 2:34 PM, James H. H. Lampert wrote:

On 12/1/17, 11:01 AM, Nathan Andelin wrote:

Unix convention. Case matters. Not that I think it was a good idea.

It gets weirder.

On my Mac (remember, Mac OS X is a fork of BSD), "echo" and "ECHO" both work like QShell "ECHO"; i.e., they don't resolve escapes (or at least, they don't resolve an "\r" escape). "echo" has a man entry, but "ECHO" does not.

On our Debian box, "echo" works like QShell "ECHO," and "ECHO" doesn't work at all.

Clearly somebody thought it was a good idea to have an "echo" that resolves escapes, and an "ECHO" that doesn't, in QShell. Not quite sure why, beyond sheer perversity and/or "cussedness."

I'm also a bit irritated that, given that keyboards lacking a caps lock key have become quite rare, SEU still defaults to uppercase-only for OPM CL. That was probably a contributing factor in my having been caught by this "gotcha."

--
JHHL