×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
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
This mailing list archive is Copyright 1997-2024 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.
midrange.com
