On save it may be difficult, given that WDSC / RDi doesn't necessarily use LPEX's save action (but an Eclipse API call instead)... It would be easier to write a user profile that detabs when the document is opened in the editor (and anyway during editing the Tab key, by default, enters spaces, rather than tab characters, in the SEU and most other LPEX editor profiles).

I usually prefer to do this kind of things manually, particularly when it's basically a one-time deal for each file.

Michael Jones wrote:
That works well! For those interested, registering an LPEX Editor / User Command of name = detab, class = com.ibm.lpex.samples.DetabCommand was all that was required (along with entering the command detab at the LPEX command line).

Do you think that it would be fairly easy to extend LPEX further by making the detab command run automatically whenever a source member is saved?

Thanks!

Mike

-----Original Message-----
From: adrian [mailto:stori@xxxxxxxxxx] Sent: Monday, December 15, 2008 2:07 PM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] LPEX - converting tabs to spaces

You must register the sample "detab" command from Window > Preferences > LPEX Editor > User Commands. By default, the command uses the current tabs setting.

For more information on detab, enter this on any LPEX command line:

?detab

For help on the tabs parameter:

?tabs

Michael Jones wrote:

In WDSC 7, is there an easy way in LPEX to convert tabs to spaces when editing or saving the source member?

I'd like the source to be indented properly if someone views the source with SEU or another editor with different tab settings.


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