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



Kelly

I don't know about the tab behavior - maybe run the "query keyaction tab" or whatever it is and see what it does - then change it in preferences. Use F1 in the command line to get a list of editor actions, etc.

At the risk of impertinence?about things landing in column 1, turn on auto formatting and set it the way you want. I know there are problems with the latest update with CL prompting and formatting. I mean, I've reverted to 5.1.2.3 so that the prompter works mostly right. ;-)

HTH
Vern

At 08:52 AM 2/22/2005, you wrote:
There's two behaviors of the CL parser I'd really like to change if possible.

(1) When I prompt a command, the parser moves the code to the far left starting position of the line on returning from the prompt.

(2) When I place the cursor within a line and press the Tab key, the cursor tabs without moving the text. For example, if my code looks like this:
ADDLIBLE LIB(MYLIB)
and I want it to look like this:
ADDLIBLE LIB(MYLIB)
I can't place my cursor at the end of ADDLIBLE and press the Tab key. I have to use the spacebar and add individual spaces.


Is there any way to change the behavior of the parser so it doesn't shift the code to the beginning of a line and so it does move the text when the Tab key is pressed?

I'm running WDSCi 5.1.2 with the CL automatic formatting and automatic indenting turned off.

Thanks,
Kelly



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.