Editing-problem newest version with PL/SQL-Developer(newest)

There is an editing problem with editing in any code in PL-SQL/Developer. The problem is solved by suspending SQL-Assistant.
The problems are (sometimes) with using the typical editing-/marking-features Shift-Left/Right/Pos1/end, Shift-CTRL-Left/Right/Pos1/end.

To reproduce one of the problems:

Go into some Code for a procedure. Go to a line with some words in a line. Press END. Now try to mark the line from end to first letter by pressing Shift-Pos1. You see: abnormal behavoir.

Next example: go to beginning of second word in a line. Press Shift-End to mark from the beginning of this word to the end of line. Next Press Shift-Left to de-mark the last letter (normally a semicolon). You see: abnormal behavoir.

There are (sometimes) other problems with marking something. Perhaps you find them by finding the one above. Without SQL-Assistant these problems are blown away.

And a small question:

is it possible to let SQL-Assistant learn to not automatically move a typed-in SQL like this:

SELECT bla
FROM dual
WHERE true=true

to

SELECT bla
FROM dual
WHERE true=true

???

Yours, Larkov.

Hi,

Thank you very much for your input. What is Pos1?

Also, could you please re-enter sample code for "SELECT bla..." using Code formatting (see "Code" icon above the edit box) This Code formatting preserves spaces and tabs in the text. In your post both "before" and "after" code samples appear identical because the web browser implicitly removes all extra spaces.

If you like you can also attach a screenshot using "Add image to post" link.

Pos1 is "position 1", meaning let the cursor go to the first textcolumn. I do not know the name on English keyboards. It is the key above the "End"-key.

The SELECT-syntax doesn't matter. :-)

I meant the "auto-indentation" if I type keys. That the other Keywords FROM, WHERE etc. are right aligned to the SELECT-Keyword.

Yours, Larkov

Pos1 on an English keyboard is called Home.

This issue is pending investigation . We will try to address it before 4.7 release.