Instead, I'd change it into a customization of the toolbar, that would solve future requests such as this ("Please add button xxx to the toolbar").

I would like to support this. I am making quite extensive use of the anjuta debugger (plug-in) and there is annoying to either press SHIFT-F12 or access menu Run->Debug program each time.
OTOH, the debugger plug-in comes with some buttons on the toolbar, namely: "Continue or suspend the execution of the program", "Run to the cursor", "Single step into the function" etc.
It would be nice if this plug-in will also include a new pair of buttons: "Run program with debugger" (the same action as pressing SHIFT-F12) and "Stop debugger". More, the menu entries under Run->Debug program, Run->Debug process, Run->debug remote target and Run->Stop debugger should be moved under the Debug menu.

> It would be nice if this plug-in will also include a new pair of buttons: "Run
> program with debugger" (the same action as pressing SHIFT-F12) and "Stop
> debugger". More, the menu entries under Run->Debug program, Run->Debug process,
> Run->debug remote target and Run->Stop debugger should be moved under the Debug
> menu.

The menu entries are under Run for a good reason, namely to make it clear that the they belong to the "Program options" dialog. Otherwise that would not be obvious. And in the end, all run a program (or attach to a running program). One could argue about "Debug process" and "Debug remote target" but I guess seperating them won't make things better.

For the toolbar, have you checked with 2.32.0 were namely #515395 is fixed? Otherwise, please report a bug against the debugger because it might be forgotten in the general bug because we don't really think about a configurable toolbar right now as gtk+ doesn't support it and it doesn't really offer that much advantage. We don't like to end up with a three (or four) line toolbar like VC++ which is super-cluttered.

Thank you for your answer, Johannes. I understand your worry about Anjuta interface becoming too cluttered, but I reiterate that I believe having the "Start debugging" and "Stop debugging" buttons on the toolbar is helpful. Just imagine that you will avoid switching between menus and toolbar or between keyboard and toolbar. The place of the two options in the menu is somewhat a secondary issue, but I still believe a better arrangement could be envisaged, maybe by reuniting the menu entries (and presumably, the plug-ins) for the menus Run and Debug.

For the record, I am using indeed Anjuta 2.32.0 on Ubuntu Maverick RC 64 and I did not encountered #515395 (it seems that it has been fixed for good). However, on the other hand, if Anjuta provides the following (thanks to Sébastien GRANJOUX):

"I have removed the suspend button in the tool bar and replaced the continue
button by a button that is doing continue or suspend depending on the debugger
state."

could it be envisaged that the same button, when FIRST pressed will start the program in the debug mode? (It should also become active after building the program, just like the "wheels" button on the toolbar.

Anyway, the bottom line is that I am still pushing for the change of having "Start debugging" and "Stop debugging" on the toolbar. I found that immensely practicable in other IDEs (I am also using Eclipse, but I am a lot closer to Anjuta philosophy of having multiple compile targets, this allows me to create test-cases on the fly - I mostly port code from other languages to C).

 (In reply to comment #4)
> Anyway, the bottom line is that I am still pushing for the change of having
> "Start debugging" and "Stop debugging" on the toolbar.

Thanks for your report. I have created a new issue for this: bug #631156 and I have replied here with more details.

Thank you. I will continue posting on the other threads.

While I think bug #631156 makes sense it is unrelated and we don't want editable toolbars in general.

Closing as WONTFIX.