This repository has been archived by the owner on Oct 26, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 35
Adds features and bug fixes. #32
Open
jmagers
wants to merge
42
commits into
seanyeh:master
Choose a base branch
from
jmagers:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
0 for startOfLine Strg+C for going to NormalMode
"e" will now work how it does in vim. Pressing "e" moves the cursor to the end of the current word. If already at the end of the word then it moves the cursor to the end of the next word.
Fixes e (end of word)
"e" can now go to the next line when there are only whitespace characters on the current line. Before this the cursor would get stuck, not moving no matter how many times you press "e" when the current line only had whitespace characters.
Another fix for e (end of word)
This allows "b" to move the cursor back a word even when the line starts with whitespace. Before this "b" would get stuck on whitespace if it was at the beginning of the line.
Fixes b/B (back word)
Before this "b" would skip the cursor over the line above it if the line was empty. It also used to skip over the previous word if that word was 1 character and was on the line above the cursor.
Another fix for b/B (back word)
The process of using back word now has fewer lines of code and better documentation.
This fixes many problems that back word was having when using the gotoPreviousWord function. Back word will now not get stuck when the current line starts with whitespace. It will also now not skip over some of the words that start on the beginning of the line. It will stop going back when it hits an empty line like in vim. It will also skip over lines that only have whitespace (just like vim).
Next-word (w) will now reach the next word when it involves moving the cursor down a line and that line starts with whitespace. It will now also skip over lines that only contain whitespace (like vim).
Fixes/improvements for: -"w" next word -"b" back word -"e" end word
New version release.
End-word (e) will now behave more like it does in vim.
End-word additonal fixes.
"cw", "dw", "cb", "db", "ce", and "de" should all now work as they do in vim.
Buf fixes for "cw", "dw", "cb", "db", "ce", "de"
"X" (capital x) will delete to the left like it does vim. Small fixes for "cw" and a few other improvements.
Adds "X" and small fix for "cw"
jmagers
force-pushed
the
master
branch
2 times, most recently
from
November 25, 2015 07:54
150155b
to
f10c4ba
Compare
"cw" and "bw" now behave more like vim in very specific conditions. "cw" and "bw" should now work as they do in vim when the cursor is on the start of a paragraph before these commands are implemented.
Makes "cw" and "bw" act more like vim.
Vibreoffice can now select by lines with "V" (visual_line mode). When in this mode lines can be selected with the j and k keys. This feature isn't perfect yet. Lines cannot yet be selected properly with the arrow keys and empty lines at the end of a selection are not always selected properly.
Adds "V" (linewise visual mode).
Vibreoffice can now correctly select any line with "V" (visual select by line) using the j and k keys. The only downside to this fix is that when selecting lines downwards with "j" the cursor will always be on the line bellow the selection. Not a big deal, just not aesthetically pleasing.
New Features: -"V", visual select by line -"X", delete to left of cursor Bug fixes: -"cw", "dw", "cb", "db", "ce", "de". -"e"
Fix for "V" (visual select by line) and Version 1.1.1 Release.
gg and G will now work in visual and visual_line mode. visual_line mode works with arrow keys.
Fixes for gg, G, and VISUAL_LINE mode.
"a" will now not move the cursor right before going into insert mode when the cursor is at the end of the paragraph. Without this fix "a" would go to the next paragraph before entering insert mode. "p" will now not move the cursor right before pasting when the cursor is at the end of the paragraph. Without this fix "p" would go to the next paragraph before pasting.
"^" will now move to the first character of the line that is not a space or a tab (more like vim). Fixed a problem with "V" where it would not select the new line character at the end of the visual base line when moving up with "k".
Bug Fixes: -"^" will now move to the first character of the line that is not a space or a tab (more like vim). -"gg" and "G" will now work in visual and visual_line mode. -Fixed a problem with "V" where it would not select the new line character at the end of the visual base line when moving up with "k". -"a" and "p" will now behave more like vim when the cursor is on the end or beginning of a paragraph.
Fix for "a" and "p".
VibreOffice defines the cursor at being at the end of a word when the cursor is to the right of the last character. Pressing "i" after following this definition would start inserting after the word and not before the last character like it does in vim. This fix changes the "e" behavior so it now will move one character to the left after reaching LibreOffice's definition of end of word in cases when it is appropriate.
Fix for "e".
LibreOffice considers a "." directly after the end of a word to be the end of word. Before this fix, pressing "e" would move the cursor to the "." in these cases instead of to the last character of the word like in Vim.
Fix for "e" in relation to words ending with a "."
Before this fix the first line selected in "V" mode wasn't always selected correctly.
@jmagers There's been no feedback since 2015-- how about releasing your own fork and opening your own issue tracker for the project? |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.