Missing is options to base the environment on either:
- the last build buildconfiguration (current implementation)
- the project environment
- a clean environment

signals which indicate that the baseEnvironment changed
some layout stuff is wrong

I don't want it in the run configurations.

rebuild the cbp file

I think that makes sense, we'll see.

We don't call it with a list anymore, so make it just a QString

Note: as for qt projects, this is also used for running. And we don't
use it for running cmake yet.

Makes it possible to reuse that code, which I intend to do for cmake and
running.

Was missing in commit efc0b208.

Reviewed-by: Roberto Raggi

Only attempt to activate the completion when there is a function id on
the left of the parenthesis.

Reviewed-by: Roberto Raggi

Handle  the 2nd parameter correctly as a event id
to be used for a handshake. Introduce a special mode
when attaching to crashed processes.
Code cleanup, pass StartParameters along to startDebugger.

The button to erase a selected color in the Fonts & Colors
(groupbox 'color scheme') was not set enabled if a color was selected,
neither was it disabled if a color had been removed using the button.

Fixes: 254202

Option for  TortoiseSVN to avoid hassle with other IDEs.

Some indenters need this information. If the C++ indenter misbehaves
based on the typed character, then that should be fixed there.

This reverts part of commit 4c07de50.

Reviewed-by: Roberto Raggi

The actions are already lazily instantiated in
TextEditorActionHandler::setupActions(), so there should be no need to
call initializeActions() in all plugins on startup. Only the main text
editor plugin will still initialize its actions, to make sure the menu
items are there.

Since we're automatically inserting several kinds of brackets, but not
braces ({ }).

The onModeChanged gets always called, even after shutdown where we
already had deleted the DebuggerManager. Don't access the 0 pointer.

works only with gbd 7.0 so far.

Makes the code nicer, we use the ProFileReader to parse the mkspec.

Introduced struct DebuggerStartParameters to pass around
start parameters, removing the need for the engines to
access private members of DebuggerManager. Pass it
to DebuggerManager::startNewDebugger() and move
the GUI parts of that function into DebuggerPlugin,
making it possible to create the struct from command line
parameters. Introduce command line parsing with a few more
-enable-xx options. Introduce warning() to debugger panel
in the CDB engine.

On this occasion, clean out a few trailing whitespaces.

At the same time, fixed the order in the QuickOpen plugin to make sure
the RefreshInterval setting isn't immediately removed after saving it.

Also disabled debug output for settings database.

Also fixed the restoring of the refresh interval, which was broken due
to different keys being used for saving and restoring.

Mainly because DocumentStates should be moved there, because it can grow
quite large. Backward compatibility is kept.

Potential replacement for QSettings. This database will allow us to save
settings incrementially, removing most of the performance issues we're
having when our few megabytes of settings are being saved.

Not done in the form of a QSettings backend because it doesn't seem the
backends can do an incremental update of the settings.

Currently used by the QuickOpenPlugin for testing.

The dock widget visibility was not saved/restored correctly, and pulling
floating dock widgets back into the layout didn't remove the header
widget in case of locked mode.
Now we track visibility and floating state of dock widgets directly.