Thanks for the responses...

Concerning setting up as SEU, I've always used the profile set as lpex,
and never had this as an issue before, at least not in WDSC. I'm not
sure what the change to SEU does to the editor, but if it dumbs it down
to SEU that won't work for me. I'll give it a try though...

Concerning not having the cursor in the prefix area, that's not the
problem - I make that mistake on occasion, but not this time.

Doug


message: 2
date: Fri, 29 Jan 2010 08:57:02 -0600
from: "Edwards, Douglas" <Douglas.Edwards@xxxxxxxx>
subject: [WDSCI-L] Prefix commands don't always work

Hello all,



I just started using RDi (version 7.5), and have pretty much got it
configured so it works like I had WDSC set up. One thing that is really
bugging me is that more often than not, I can't get the prefix commands
to work. I key in the CC and CC commands, and then an A command to copy
the code block, and when I hit the Enter key, all that happens is the
commands disappear and I get a blank line inserted. Then, a little
while later I may try it again, and this time it works. Don't know why
it doesn't always work, and don't know what has happened in between to
suddenly make it work.



Thanks



_____________

The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.
_____________

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.