We don't support blocks yet, and this way we get rid of quite some
parsing errors (resulting in undefined or wrongly defined types, messing
up the semantic passes).

Reviewed-by: Roberto Raggi

The project selector also allows to select targets.
However, this is not yet used, since the necessary
changes are still being stabilized.

Done-with: con

In the model should be written once at time. The Locker is there to
detect other cases. Many calls are commented out because this is now the
case.

ex commands might depend on current cursor position and might modifiy
it, thus set the editor's text cursor to fakevim's before initiating the
command and use the editor's text cursor afterwards

Merge-request: 101
Reviewed-by: hjk <qtc-committer@nokia.com>

this behaviour seems more natural to me, but it has one draw-back: if an
action associated to a shortcut is not enabled, typing that shortcut won't
leave passing mode

forwarding keys with empty text() does not restrict the matching items, but
updating the list of possible completions resets the currently selected item to
the first one

Task-number: QTCREATORBUG-235

- cursor position should be the start of the yanked region
- the number of lines yanked should be displayed, even when motion was not linewise

Merge-request: 99
Reviewed-by: hjk <qtc-committer@nokia.com>

Merge-request: 99
Reviewed-by: hjk <qtc-committer@nokia.com>

Merge-request: 99
Reviewed-by: hjk <qtc-committer@nokia.com>

Merge-request: 99
Reviewed-by: hjk <qtc-committer@nokia.com>

Merge-request: 99
Reviewed-by: hjk <qtc-committer@nokia.com>

Merge-request: 99
Reviewed-by: hjk <qtc-committer@nokia.com>

expected cursor position is on last character which was replaced

Merge-request: 99
Reviewed-by: hjk <qtc-committer@nokia.com>

Merge-request: 99
Reviewed-by: hjk <qtc-committer@nokia.com>

Merge-request: 99
Reviewed-by: hjk <qtc-committer@nokia.com>

Merge-request: 99
Reviewed-by: hjk <qtc-committer@nokia.com>

mostly cursor positions have been changed

Merge-request: 99
Reviewed-by: hjk <qtc-committer@nokia.com>

Merge-request: 99
Reviewed-by: hjk <qtc-committer@nokia.com>

Merge-request: 99
Reviewed-by: hjk <qtc-committer@nokia.com>

- apparently one additional empty line is added to the document at its end,
  if the last line ends with \n

Merge-request: 99
Reviewed-by: hjk <qtc-committer@nokia.com>

- previously, if the visible vi cursor is on the last character of a line,
  the corresponding QTextCursor might have been positioned before and after
  the character
- code becomes simpler if the QTextCursor is always positioned before the
  vi cursor

Merge-request: 99
Reviewed-by: hjk <qtc-committer@nokia.com>

Merge-request: 99
Reviewed-by: hjk <qtc-committer@nokia.com>