GitLab

line wrap were appended, also appendOutput and appendOutputInline ended
up doing almost the same thing. It might be that appendOutput is called
in some places where appendOutputInline would be more adequate. The code
now tries to called QPlainTextEdit::appendPlainText() whenever it can
because of its update optimizations when it comes to enforcing maximum
block count. We want application output to be processed fast, even if
the maximum block count was reached!

Reviewed-by: dt

Reviewed-by: Trust Me

Conflicts:

	src/libs/cplusplus/CppBindings.cpp
	src/libs/cplusplus/CppBindings.h
	src/libs/cplusplus/FastPreprocessor.cpp
	src/libs/cplusplus/FastPreprocessor.h
	src/plugins/cpptools/cppcurrentdocumentfilter.cpp
	src/plugins/cpptools/cppcurrentdocumentfilter.h
	src/plugins/cpptools/cppsemanticsearch.cpp
	src/plugins/cpptools/cppsemanticsearch.h
	src/plugins/duieditor/parser/qmljs.g
	src/plugins/duieditor/parser/qmljsast.cpp
	src/plugins/duieditor/parser/qmljsast_p.h
	src/plugins/duieditor/parser/qmljsastfwd_p.h
	src/plugins/duieditor/parser/qmljsastvisitor.cpp
	src/plugins/duieditor/parser/qmljsastvisitor_p.h
	src/plugins/duieditor/parser/qmljsengine_p.cpp
	src/plugins/duieditor/parser/qmljsengine_p.h
	src/plugins/duieditor/parser/qmljsgrammar.cpp
	src/plugins/duieditor/parser/qmljsgrammar_p.h
	src/plugins/duieditor/parser/qmljslexer.cpp
	src/plugins/duieditor/parser/qmljslexer_p.h
	src/plugins/duieditor/parser/qmljsmemorypool_p.h
	src/plugins/duieditor/parser/qmljsnodepool_p.h
	src/plugins/duieditor/parser/qmljsparser.cpp
	src/plugins/duieditor/parser/qmljsparser_p.h
	src/plugins/duieditor/parser/qmljsprettypretty.cpp
	src/plugins/duieditor/parser/qmljsprettypretty_p.h
	src/plugins/duieditor/rewriter/rewriter.cpp
	src/plugins/duieditor/rewriter/rewriter_p.h
	src/plugins/duieditor/rewriter/textwriter.cpp
	src/plugins/duieditor/rewriter/textwriter_p.h
	src/shared/cplusplus/ASTClone.cpp
	tests/manual/cplusplus/main.cpp

Reviewed-by: Trust Me

This one has some magic inside to always use the current outputpane.
This solves the issue that I don't want Search and Build Issues list to
have its own set of next/prev shortcuts. todo is a better definition of
next for the build issues and/or a way to restrict it only to errors.

Removed "void" from functions that take no parameters, removed a few
"get" prefixes, etc.

Details:  We should stop all running runners, while the plugins are
still alive.

- drop prefix magic
- avoid inserting stray newlines

this also fixes the overquoting of app output.

Default shortcut is Ctrl+Shift+R now, but maybe there's something better
or more widely accepted. No menu entry yet.

Changing nothing, just preventing next patch to be scrambled by it.