cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

ADT 3.48 bug - Delete and Ctrl-Z keys are deactivated after Ctrl-F (Find/Replace) used. Workaround?

Sandra_Rossi
Active Contributor
1,304

After I use Ctrl-F to find or replace any text in an ABAP source code, the Delete key doesn't delete any more.

Hopefully I can use the backspace key but that's quite annoying.

Ctrl-Z is also deactivated.

Any nice workaround to get them back?

Thanks.

Sandra

Version: Eclipse 2025-03 / ADT 3.48

Accepted Solutions (1)

Accepted Solutions (1)

Sandra_Rossi
Active Contributor
0 Likes
I have created a ticket at SAP Support (note for myself: case 1303039/2025 under my company). They confirmed Nov 14th that the bug was reproduced, and the fix will be part of the 2602 ADT plugin.
The bug is related to the use of the new search dialog.
Until February 2026, there are these workarounds:
  1. Use the old search dialog
  2. If you want to use the new search dialog, press Ctrl+F7 twice each time the bug happens
  3. Use Backspace instead of Delete, right click Undo instead of Ctrl+Z 

 

WORKAROUND 1, as proposed by SAP Support:

  • "You can disable the "new" search dialog in eclipse and get back the old dialog: In the preferences, General > Editors > Text Editors untick the checkbox Use find/replace overlay
    With the old find/replace dialog the issue should not occur."

Sandra_Rossi_0-1763628060388.png

Sandra_Rossi_1-1763628116919.png

WORKAROUND 2: the Delete key and Ctrl+Z key come back if you change the current ADT view, for instance by pressing Ctrl+F7 twice.

WORKAROUND 3: you may also use these alternatives:

  • Backspace key instead of Delete
  • Right-Click > Undo instead of Ctrl+Z

Answers (1)

Answers (1)

Sandra_Rossi
Active Contributor

WORKAROUND:

The Delete key and Ctrl+Z key come back if you change the current ADT view, for instance by pressing Ctrl+F7 twice.

If pressing Ctrl+F7 twice becomes annoying, you may also use these alternatives:

  • Backspace key instead of Delete
  • Right-Click > Undo instead of Ctrl+Z

NB: both the question and the answer concern the keyboard problem after pressing Ctrl+F.

SAP Support proposed this better workaround:

  • "You can disable the "new" search dialog in eclipse and get back the old dialog: In the preferences, General > Editors > Text Editors untick the checkbox Use find/replace overlay
    With the old find/replace dialog the issue should not occur."

Sandra_Rossi_0-1763628060388.png

Sandra_Rossi_1-1763628116919.png

ptrck
Explorer
0 Likes
Do you also have problems navigating between tabs? So with Ctrl+PageUp/Down? It no longer works properly for me. The navigation direction is mixed up and in classes it jumps to the “Test Classes” sub-tab. Does anyone else have this problem? I have reinstalled Eclipse and the ADTs and before installing the ATDs the navigation still worked. Afterwards not anymore!
Sandra_Rossi
Active Contributor
0 Likes

@ptrckI navigate via Ctrl+E (AKA Ctrl+F6), I don't use Ctrl+Page Down and Page Up. If I try, it seems to work identically whatever it's before or after pressing Ctrl+F.

If your question concerns Ctrl+Page Down and Page Up in a previous Eclipse version versus now, I don't know, but you may ask your own question or contact SAP Support.

NemanjaSimovic
Participant

This still is not solved, and it's so annoying to do all the time Ctrl+F6 to bring back Delete key. 😤 Thanks @Sandra_Rossi  for reporting. 👍

Sandra_Rossi
Active Contributor
0 Likes
@NemanjaSimovic Thanks for correcting me, I guess I was confused. I confirm too that the bug is not fixed (I have just checked on my ABAP backend versions), I have fixed my answer, made it NOT a solution, and reported the bug to SAP (note for myself: case 1303039/2025 under my company).
Sandra_Rossi
Active Contributor
0 Likes
I realize that right after starting Eclipse, there's no bug after pressing Ctrl+F. It happens only after a number of actions; I can't say what are the minimal steps to reproduce the problem.
Sandra_Rossi
Active Contributor
0 Likes

Good news, SAP Support confirmed Nov 14th that the bug was reproduced, and the fix will be part of the 2602 ADT in Eclipse version.