| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
| |
columnNumber() relies on text wrapping, and we're only interested in the
position of the cursor in the block.
|
|
|
|
|
|
| |
Also removed TokenUnderCursor as it's functionality is in the token cache.
Reviewed-by: ckamm
|
|
|
|
| |
This reverts commit c2393df02332618c8cf6159d9d6f6a40041ced89.
|
|
|
|
|
| |
This should speed things up a bit, because before, the line was tokenized at
least 3 times.
|
| |
|
| |
|
|
|
|
| |
not sorted.
|
|
|
|
|
|
| |
Don't sort the global completion items when we have too many of them, instead
populate the completion box in a way where local symbols are showed before
global symbols.
|
| |
|
|
|
|
| |
This reverts commit 13a721d985aa04de3ded3c3049179512469ec0f7.
|
|
|
|
| |
This reverts commit bb35b4d0811b0b4a3f198af0ae749f32950bfd28.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
To only run if the pound/hash sign is at the start of the line.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| | |
Conflicts:
src/plugins/cpptools/cppcodecompletion.cpp
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
By moving the completion settings into the TextEditor plugin, so that
both the CppTools and the QmlJSEditor plugins can access the settings.
The user-interface to edit the settings is still in the CppTools plugin,
since we're in string freeze at the moment. It should be moved to the
TextEditor plugin later.
For now the QML completion only supports the case-sensitivity and
partial completion options, since there is no automatic insertion of
brackets.
Task-number: QTCREATORBUG-1327
Reviewed-by: Daniel Molkentin <daniel.molkentin@nokia.com>
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
new LookupContext.
|
|/ |
|
|
|
|
| |
Reviewed-by: mae
|
|
|
|
| |
The fake tooltip duplication is not nice.
|
|
|
|
|
| |
Reviewed-by: mae
Merge-request: 133
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The problem was that for
Foo::Foo
(|)
when the user triggers completion at |, startOfLine() returns a token
that's not on the current line and not yet tokenized by that instance
of the BackwardScanner.
As a fix I explicitly ask the instance to tokenize up to the given
index.
Task-number: QTCREATORBUG-673
Reviewed-by: Roberto Raggi
|
|
|
|
|
|
| |
Fixes QTCREATORBUG-787
Reviewed-by: Erik Verbruggen
|
| |
|
| |
|
|
|
|
| |
This reverts commit 2a59d2ae0c889fe6e4ac50a3f110b0103f880c15.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Because apparently, while designing the Objective-C language, somebody
thought it was a world-class idea to allow any white-space between the
'@' character and the subsequent keyword. With this fix, we now
correctly parse:
@ dynamic
and:
@
selector
and:
@"foo"
"bar"
@"mooze"
(This last one is 1 single string split over multiple lines.)
Wonderful, isn't it?
What we (and Clang) do not support, but what GCC supports is something
like:
@"foo"@@ "bar" @"mooze" @@
which is equivalent to @"foobarmooze".
|
|
|
|
| |
foreach()-Loops.
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
doc/qtcreator.qdoc
doc/qtcreator.qdocconf
src/app/Info.plist
src/plugins/bineditor/BinEditor.pluginspec
src/plugins/bookmarks/Bookmarks.pluginspec
src/plugins/cmakeprojectmanager/CMakeProjectManager.pluginspec
src/plugins/coreplugin/Core.pluginspec
src/plugins/coreplugin/coreconstants.h
src/plugins/cpaster/CodePaster.pluginspec
src/plugins/cppeditor/CppEditor.pluginspec
src/plugins/cppeditor/cppeditor.cpp
src/plugins/cpptools/CppTools.pluginspec
src/plugins/cvs/CVS.pluginspec
src/plugins/debugger/Debugger.pluginspec
src/plugins/debugger/debuggeragents.cpp
src/plugins/debugger/gdb/gdbengine.cpp
src/plugins/designer/Designer.pluginspec
src/plugins/fakevim/FakeVim.pluginspec
src/plugins/find/Find.pluginspec
src/plugins/genericprojectmanager/GenericProjectManager.pluginspec
src/plugins/git/ScmGit.pluginspec
src/plugins/helloworld/HelloWorld.pluginspec
src/plugins/help/Help.pluginspec
src/plugins/locator/Locator.pluginspec
src/plugins/perforce/Perforce.pluginspec
src/plugins/projectexplorer/ProjectExplorer.pluginspec
src/plugins/qmleditor/QmlEditor.pluginspec
src/plugins/qmleditor/idcollector.cpp
src/plugins/qmleditor/idcollector.h
src/plugins/qmleditor/parser/qmljsglobal_p.h
src/plugins/qmleditor/qmlcodecompletion.cpp
src/plugins/qmleditor/qmlcodeformatter.cpp
src/plugins/qmleditor/qmlcodeformatter.h
src/plugins/qmleditor/qmlexpressionundercursor.cpp
src/plugins/qmleditor/qmllookupcontext.cpp
src/plugins/qmleditor/qmlresolveexpression.cpp
src/plugins/qmleditor/qmlsymbol.cpp
src/plugins/qmleditor/qmlsymbol.h
src/plugins/qmlprojectmanager/QmlProjectManager.pluginspec
src/plugins/qt4projectmanager/Qt4ProjectManager.pluginspec
src/plugins/qtscripteditor/QtScriptEditor.pluginspec
src/plugins/regexp/RegExp.pluginspec
src/plugins/resourceeditor/ResourceEditor.pluginspec
src/plugins/snippets/Snippets.pluginspec
src/plugins/subversion/Subversion.pluginspec
src/plugins/texteditor/TextEditor.pluginspec
src/plugins/vcsbase/VCSBase.pluginspec
src/plugins/welcome/Welcome.pluginspec
src/shared/qml/parser/qmljsast.cpp
src/shared/qml/parser/qmljsast_p.h
src/shared/qml/parser/qmljsastfwd_p.h
src/shared/qml/parser/qmljsastvisitor.cpp
src/shared/qml/parser/qmljsastvisitor_p.h
src/shared/qml/parser/qmljsengine_p.cpp
src/shared/qml/parser/qmljsengine_p.h
src/shared/qml/parser/qmljsgrammar.cpp
src/shared/qml/parser/qmljsgrammar_p.h
src/shared/qml/parser/qmljslexer.cpp
src/shared/qml/parser/qmljslexer_p.h
src/shared/qml/parser/qmljsmemorypool_p.h
src/shared/qml/parser/qmljsnodepool_p.h
src/shared/qml/parser/qmljsparser.cpp
src/shared/qml/parser/qmljsparser_p.h
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Avoids some annoyance for people using case-sensitive completion, when
unrelated completions items would get higher relevance because they
start with the typed string when matched case-insensitively.
In case-insensitive mode, a case-sensitive prefix match now does get a
higher relevance than a case-insensitive match.
Reviewed-by: con
|