Re: Re: Skeleton records and auto indent missing in JLPEX? -- WDSCI-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.

Thanks, Adrian

Ah, I see why skeleton did not work for me. It behaves differently - the S stays after pressing ENTER, then disappears on the first IS. Also, you need, apparently, to enter IS for each skeleton you want to insert - it does not keep inserting skeletons, as SEU does - even though I was in SEU mode. I understand this is long standing - I think regular CODE is lacking here(IMO) as well. A design choice, I suppose. I'm glad you will look into it - it has a lot more benefit for me that way. One thought - it probably needs to go with Replace mode instead of Insert mode.

Did not know about Ctr;-R, just tried it, and will tell others here about it - most are using CODE so far, I'm the bleeding-edge pioneer. ;-)

Vern

At 08:22 PM 9/13/2003 -0400, you wrote:

The SEU base profile does support the S and ISn prefix commands, granted without the cursor positioning (as the JLPEX cursor must be in the prefix area in order to process the prefix commands). I'll take a look how cursor positioning could be added.

In addition, several document parsers support some basic keyword expansion, with cursor positioning (like it is in CODE), activated by Ctrl+R - e.g., in C/C++, for: for case, do, doc, for, if, main, switch, try, while. In WDSC 5.1 you will be able to add/redefine your own expansions (even though not via a dialog yet) e.g.,

set parserProperty.proto.cpy (C) MyCompany 200?. All Rights Reserved.

I believe there is also some work underway for more serious template support for certain parsers (RPG?). Not sure right now about auto indent in C/C++.

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.