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



Jim,

The changes should persist if you make them via the Window > Preferences :
LPEX Editor > User Key Actions settings. I know the first time I tried in
response to your original post, it did not seem to work. Then I discovered
that It works as expected in a CL source member, but in an RPG member does
not obey my remapping of the enter key. the numpadEnter key will obey the
override, just not the enter key.

Make sure you add the key mapping change, then SET to keep it and Apply to
really make sure it is saved. ;^)

Is anyone else having issue with RDi 9.0 and the enter key mapping not
obeying the override in RPG?

Jim


On Tue, Jul 23, 2013 at 6:26 AM, Jim Oberholtzer <
midrangel@xxxxxxxxxxxxxxxxx> wrote:

Thanks Paul and Buck, that's exactly what I wanted! I like the split
line function too.

How do you make those changes persistent between RDP starts?

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 7/23/2013 7:12 AM, Paul Bailey wrote:
You can set the Enter key using "set keyAction.enter newLine" in the
LPEX command line, to try out that method for the ENTER key (which I think
is what you want.) Use "set keyAction.enter openLine" to go back to the
default, or just close and re-open the RDP application. ("query
keyAction.enter" will tell you what it is set to.)

If "newLine" is not to your taste, then perhaps just remap to "down"
instead (as in the cursor down key).

If you type "?samples" (w/o quotes) in the command line of the LPEX
editor (from a source member in RDP, press ESC to get to the LPEX command
line) and the help screen will (eventually) show various sample classes
that you can add to key actions, eclipse "user profiles", etc. Some of
those samples work right off the bat, and others require a little work, but
the source is there and will give you all sorts of clues for getting your
environment just the way you like it.

Personally, I have the enter keys set as follows:
set keyAction.enter down
set keyAction.s-enter openLine
set keyAction.numpadEnter splitAndShift
set keyAction.s-numpadEnter splitLine


-Paul.



-----Original Message-----
From:wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Buck Calabro
Sent: 22 July 2013 18:18
To:wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] turn off automatic line insert when enter key
pressed.

On 7/22/2013 11:46 AM, Jim Oberholtzer wrote:
RDP 8.0.3. ( to lazy to update at this point, I really should )

I am almost always editing existing source, rather than creating new.
I've tried to find the switch in the CL parsers to stop the enter key
from automatically inserting a new line. Instead I would prefer it
simply commits the change I just made and takes the cursor to the
next
line.

My suggested behavior might drive someone creating new code nutty,
but
it will save me time and aggravation since mostly I'm modifying code
I've copied into the member.

Is there a way to do it?
Try setting a User Key Action. Windows> Preferences> LPEX Editor>
User Key Actions

for Key, specify enter
for Action, select newLine
Click Set on the right, then Apply.
--buck
--
--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & 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-Ups:
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.