× 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.


  1.  Home
  2. MIDRANGE-L
  3. December 2001

RE: Command Message Ids

Al,

I don't mind so much, but if it's still there, I agree it should it be
updated...?  Or yank 'em and provide option to print list of cmds/IDs from
online text.  (And/or InfoCenter, I s'pose...)

JMHO.  (And still working on other replies.)

jt

| -----Original Message-----
| From: midrange-l-admin@midrange.com
| [mailto:midrange-l-admin@midrange.com]On Behalf Of
| barsa@barsaconsulting.com
| Sent: Friday, December 14, 2001 10:35 AM
| To: midrange-l@midrange.com
| Subject: RE: Command Message Ids
|
|
|
| This appendix from the CL reference manual has not been updated
| for several
| releases.
|
| Shame on big blue.
|
| Al
|
| Al Barsa, Jr.
| Barsa Consulting Group, LLC
|
| 400>390

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.