Feature request: Do not process key action on AutoReplace

zakko

Member³
An auto replace command is triggered with "Space" or "Enter" key. In both cases it's mostly not useful to have the blank or linebreak executed right after the replacement.

Solution would be, that PL/SQL Developer only executes the replacement but not the explicit key action.

 
You can go to Preferences > Key Configuration and define a key for the "Editor: AutoReplace" function. Now you can either use a space or enter (which would be inserted in the text) or the function key (in which case no additional text is inserted).
 
Thanks for the info. For me personally (maybe others agree...) the space bar is the best option as auto replace trigger to preserve coding flow. This preference is the reason, why I was asking.

But I checked some other single keys (without Ctrl or Alt) even with Shift as keyboard shortcut, but all of them also trigger the respective key action in addition to the auto replacement.

As you said, it is also possible with key + Ctrl/Alt, but I think this distinctly interferes with the typing flow at that point. Partly a question of taste of course, but maybe this could be worth another improvement...
 
Thanks to this thread I was able to use a COMMA as a key for my text expansion!

This helps when typing column expansions in a select list. Prior to this discovery I had to hit space before the comma.
 
Back
Top