Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Why every IDE has different keyboard shortcuts for debugging? [closed]

Every developer knows the 5 basic operations that IDEs allow to perform during a debug:

  1. step into
  2. step over
  3. step return
  4. resume
  5. terminate

(according to Eclipse vocabulary)

Now take a look to the keyboard shortcuts assigned to them, in some IDEs taken as examples:

  • Eclipse:
    1. F5
    2. F6
    3. F7
    4. F8
    5. Ctrl+F2
  • Borland C++ Builder 5:
    1. F7
    2. F8
    3. Shift+F8
    4. F9
    5. Ctrl+F2
  • Visual Studio 2010:
    1. F11
    2. F10
    3. Shift+F11
    4. F5
    5. Shift+F5
  • Firefox debugger:
    1. F8
    2. F7
    3. Shift+F8
    4. F6
  • Chrome debugger:
    1. F11
    2. F10
    3. Shift+F11
    4. F8

It's a mess... I usually develop with all of them (and more) and I can never remember the correct buttons...

So the question is:

why these configurations are nowhere near standardized? Is there a project to standardize them?

How do you deal with this daily issue? Changing the configuration for each IDE? In this case which "standard" configuration do you choose? Many thanks!

like image 699
bluish Avatar asked Jun 08 '11 12:06

bluish


People also ask

Why do I need an IDE debugger?

0 With an IDE debugger you can see the values of ALL the variables in the current scope (all the way up the call stack) whenever you halt execution. Print statements can be great but dumping so much information to the screen at any given place can produce a wholelot of print statements.

Why is IntelliJ IDEA not detecting my keyboard shortcuts?

If your keyboard does not have an English layout, IntelliJ IDEA may not detect all of the shortcuts correctly. The following table lists some of the most useful shortcuts to learn: Quickly find any file, action, symbol, tool window, or setting in IntelliJ IDEA, in your project, and in the current Git repository.

How to debug a bug?

Even if we manage to solve the issue once, that won’t happen every single time and clearly this is not a very good approach to solve any bug. The debugging process can be divided into four main steps: localizing, classifying, understanding, and finally repairing the bug. Localizing means identifying where the bug is in the code.

What are the steps of debugging in software testing?

The debugging process can be divided into four main steps: localizing, classifying, understanding, and finally repairing the bug. Localizing means identifying where the bug is in the code. A particular service or function might be responsible for producing the bug.


1 Answers

The only solution to this problem I have seen is that some IDEs ship with key-mappings for other IDEs, for example Netbeans has a "Eclipse" preset in its key-mappings options.

The problem with this is the same as OSX using Cmd vs Windows/Linux using Ctrl IMO. Everyone started doing things their own way, and nobody wants to be the one giving up their way, especially since it would piss off their users. Maybe with time most of it will slowly be standardized, with new IDEs adopting standards and old ones dying, but I don't see this happening anytime soon.

like image 55
Seldaek Avatar answered Nov 15 '22 19:11

Seldaek