Add new stop characters for nextWord and prevWord actions

Thank you for taking the time to submit your request. After careful consideration, we know that we cannot deliver your requested enhancement in the near term, so it is being declined. However, your request does align with the future strategy of our product and we believe it may have future value, so we will add it to an internal list for us to keep in mind for the future.

We have reviewed this requirement and we feel it would be a beneficial enhancement to the product. We hope to be able to add it to our development plans in the future.

I think this is a great idea and would be most useful extending it to CL, COBOL, DDS, etc.--i.e., it should function this way in LPEX no matter what the source type is.

Although the theme of this request is consistent with our business strategy, it is not committed to the release that is currently under development.

Sorry, I forgot: One exception is the dot in qualified data structures. It should definitely be treated as a word separator, same for (,), and ;. In this I agree with Matt's reply to JMarkMurphy.

I think usually you don't want to stop inside a variable's name, you want to skip the variable and get to the next "entity" (command, operator, comment etc).

So I think it's helpful in a source code editor to consider a variable a word. In contrast to Matt, to me it's annoying when some tools don't. So I support JMarkMurphy's suggestion "to use a key other than ctrl-> or ctrl-<".

Mark no where do I ask for anything more complicated than stopping at a punctuation character. If there is no characters like this then stopping at anything else like a letter or number is not reasonable.

If you use the IBM ACS or I Nav Run SQL Scripts (or any other source editor not LPEX, try out editing an SQL script with the SQL and XQuery Editor) and use the next word short cut (CTRL+Right arrow) the next stop point is a punctuation character like " " , . ( ) ' ' / : ; LPEX should stop at characters like these tools do.

I would be okay if the next word stop character only expanded to ( ) : and ;.

>> variable = long_datastructure_array(idx).sub_field_within_DS-_arry;
>> results = LongProcedureNameBecuaseWeWantMeaningfulNames

So in the above, if the cursor is in datastructure, ctrl-> would jump to the first character of array, and if you were in Procedure, it would jump to the N in Name?

The requirements would have to be specified very specifically, and you still couldn't have something like starting from d in datastructure it would jump to the s in data structure without some word dictionary. Even then it would not be very accurate due to all the funky abbreviations we use to name variables. This has to work for everyone's coding style, not just yours.

So what would a reasonable next word look like if words aren't delimited by spaces and punctuation? The next capital (probably not, see DS above)? The next capital after a lower case letter? The next letter after an underscore?

I think it would have to use a key other than ctrl-> or ctrl-< though because we are all used to how those work, and what a word is.

A preliminary evaluation of this request indicates that it is consistent with our business strategy. Further evaluation of this RFE is underway.