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

Reviewed-by: Roberto Raggi

Joel Nordell (1):
      XCode-style tab behavior

Request-url: http://gitorious.org/qt-creator/qt-creator/merge_requests/542


Reviewed-by: Thorbjørn Lindeijer <thorbjorn.lindeijer@nokia.com>

Fixes performance issue with typing opening parentheses.

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.

Make operator% only act on types we want to handle.
Also add a benchmark for comparison with QString::reserve();

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

Drop original QStringBuilder class, rename QStringBuilderPair to
QStringBuilder. Put everything except the QLatin1Literal class and
the global operator%() in a private namespace.

When starting a line with :, the indenter now no longer removes the
indentation. Usually you do this when you're typing the global scope
operator.

Reviewed-by: Roberto Raggi

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 ({ }).

which basically means cutting features. heh

this also removes the optimization to skip test function calls which
appear to be part of a failed test, as this could skip includes, etc. as
well.

an evaluation function can be an include statement. the included code
must neither inherit nor change the current inversion state.

to enable cleaner save/restore - for later

functions which have essentially two return values are kinda confusing.
so represent file & parse errors as false in the regular evaluation
result (like qmake effectively does).

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.