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



That didn't work. Good try, though.
Kelly

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx
[mailto:wdsci-l-bounces@xxxxxxxxxxxx]On Behalf Of
MWHopkins@xxxxxxxxxxxxxxx
Sent: Friday, February 25, 2005 8:51 AM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] Question about LPEX Editor behavior


Try placing your cursor in front of '-name', then while holding the shift 
key move the cursor to the end of the previous line (where you want 
'-name'). This should highlight all the spaces between the two, then hit 
delete.

Matt Hopkins 
Sr. Programmer/Analyst 
Web: www.pdpgroupinc.com 
Email: MWHopkins@xxxxxxxxxxxxxxx 
Office: 410-584-0330 
Fax: 410-584-0336 





"Kelly Cookson" <KCookson@xxxxxxxxxxxx> 
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
02/25/2005 09:42 AM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
"Websphere Development Studio Client for iSeries" <wdsci-l@xxxxxxxxxxxx>
cc

Fax to

Subject
[WDSCI-L] Question about LPEX Editor behavior






The behavior of my LPEX editor seems to have changed, and I'm missing 
something on how to change it back.

Suppose I have accidentally pressed the Enter key and split a line as 
follows:

000001                           01  WS-MY-VARIABLE
000002                -NAME              PIC X(10).

What I'd like to do is using my backspace key or delete key to remove the 
spaces between VARIABLE and -NAME to put the line back together again.

Now, however, if I position my cursor in front of the -NAME, I can 
backspace to the beginning of the line but no further. It gets to this 
point and stops:

000001                           01  WS-MY-VARIABLE
000002-NAME                              PIC X(10).

Pressing backspace does nothing else. Nor does placing the cursor after 
WS-MY-VARIABLE  and pressing the delete key bring the line back together. 
Basically, I have to cut and paste, which takes me longer and is annoying.

I'm pretty sure I remember being able to bring lines back together with my 
backspace or delete keys. What did I do to change the editor behavior? How 
can I change it so my backspace or delete keys will bring two lines 
together?

Also, I have gone to Window > Preferences > Remote Systems > iSeries > 
LPEX Editor Parsers > COBOL a couple of times now and made sure the 
automatic syntax checking box was unchecked. I definitely checked the 
Apply button. I've even restarted WDSCi and my PC to make sure changes 
took effect (though this should really have nothing to do with it). Yet, I 
still messages popping up regarding syntax while I code.  For example, if 
I split a line, I might see this:

Thanks,
Kelly
-- 
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.

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


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.