× 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. WDSCI-L
  3. January 2008

Re: WDSc / RSE LPEX Editor - Column Sensitive Editing - Y or N

I don't think CL has an issue, but COBOL does when shifting source. COBOL
has 3 or 4 columns that cause issues when column sensitivity is on. Makes
it harder to go between DDS and COBOL source editing.

On Jan 30, 2008 12:11 PM, Brian Johnson <brian.johnson.mn@xxxxxxxxx> wrote:

On Jan 30, 2008 10:18 AM, Jim Essinger <dilbernator@xxxxxxxxx> wrote:

I have a request to IBM WDSC developers to change the placement of the
column sensitivity setting. I wanted them to relate it to the type of
source being edited. I want column sensitivity in DDS and RPG, but not
in
COBOL and CL. I have mine at 'N' because I am mostly editing CL and
COBOL,
and it does not make sense there.


I've not noticed that column sensitive editing does anything with CL
source. What am I not noticing that I should be annoyed with?


--
Brian Johnson
brian.johnson.mn@xxxxxxxxx
--
This is the Websphere Development Studio Client for iSeries (WDSCI-L)
mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...
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.