this way, users can override these commands with arbitrary actions,
some want to map switching between the opened files to these keys
Merge-request: 101
Reviewed-by: hjk <qtc-committer@nokia.com>
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
- 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>
- 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>
the lines touched by the motion have to be removed completely except for one newline
(whereas 'd' removes them including all newlines)
Merge-request: 99
Reviewed-by: hjk <qtc-committer@nokia.com>
- make '~' repeatable with '.'
- implement operators 'gu'/'gU'/'g~' for down-casing/up-casing/case-inversion
- visual char/line/block modes for the above
Merge-request: 99
Reviewed-by: hjk <qtc-committer@nokia.com>
previously, the first character typed in command mode would have been inserted into the document
Merge-request: 99
Reviewed-by: hjk <qtc-committer@nokia.com>
- allow for handling unknown arguments to ':set' by the layer having installed the FakeVim handler
- use that to change the Find plugin's case sensitivity
Merge-request: 97
Reviewed-by: hjk <qtc-committer@nokia.com>
the find plugin places the cursor at the end of a found item, but vi at the start,
thus update cursor position when editor widget regains focus
Merge-request: 97
Reviewed-by: hjk <qtc-committer@nokia.com>
use creator's indenter for smartindent mode
- this works like automatic indent w/o fakevim
perhaps this fixes QTCREATORBUG-139
Merge-request: 98
Reviewed-by: hjk <qtc-committer@nokia.com>
in order for automatic indenting to work, isElectricCharacter has to match the language of the document
Merge-request: 98
Reviewed-by: hjk <qtc-committer@nokia.com>
- the indented region has been off by one line as lineForPosition returns 1-based line numbers but QTextDocument::findBlockByNumber expects base 0
- all lines (including first and last line) have to be indented
- if text is collapsed, then findBlockByNumber has to be used instead of findBlockByLineNumber for getting the block containing a line
Merge-request: 96
Reviewed-by: hjk <qtc-committer@nokia.com>
