Code (LPEX) in WDSC V5 -- CODE400-L

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

Subject: Code (LPEX) in WDSC V5
From: "Jon Paris" <Jon.Paris@xxxxxxxxxxxxxx>
Date: Tue, 22 Jul 2003 18:24:43 -0400
Importance: Normal
List-archive: <http://archive.midrange.com/code400-l>
List-help: <mailto:code400-l-request@midrange.com?subject=help>
List-id: CODE/400 Discussion & Support <code400-l.midrange.com>
List-post: <mailto:code400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/code400-l>,<mailto:code400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/code400-l>,<mailto:code400-l-request@midrange.com?subject=unsubscribe>

 >> So, in most cases when people refer to LPEX they are talking about the
editor in CODE/400. When they talk about JLPEX, they are talking about the
editor in WDSC/RSE.

Thanks for such a succinct summary Scott.

IBM please take note - you introduced the notion of calling the new version
jLPEX - Please Please Please go back to calling it that!!  The current
practice of calling the _new_ editor lpex is unbelievably confusing (to put
it politely).

Jon Paris
Partner400
www.Partner400.com

As an Amazon Associate we earn from qualifying purchases.

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.