aboutsummaryrefslogtreecommitdiff
path: root/src/nvim/ops.c
diff options
context:
space:
mode:
authorJack Danger Canty <jackdanger@squareup.com>2015-01-19 22:21:14 -0800
committerJack Danger Canty <jackdanger@squareup.com>2015-01-22 21:57:03 -0800
commit19c22cdb80e30711be5af33cb6726566ad629944 (patch)
treee83b3e922b402921da48d721b7b8199b6a0a62f2 /src/nvim/ops.c
parentd550eecf7092397d064df26850d4a09d9ab4a481 (diff)
downloadrneovim-19c22cdb80e30711be5af33cb6726566ad629944.tar.gz
rneovim-19c22cdb80e30711be5af33cb6726566ad629944.tar.bz2
rneovim-19c22cdb80e30711be5af33cb6726566ad629944.zip
"halfway a line" is a very confusing phrase
If you Google for this phrase found in the Vim documentation you'll find almost exclusively hits from the Vim documentation. I think changing "halfway a line" to "halfway through a line" makes more sense. There seems to be an pervasive odd use of the word 'halfway' in the original docs which I'm updating everywhere.
Diffstat (limited to 'src/nvim/ops.c')
-rw-r--r--src/nvim/ops.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/nvim/ops.c b/src/nvim/ops.c
index 90fc89ee21..90cb482ec5 100644
--- a/src/nvim/ops.c
+++ b/src/nvim/ops.c
@@ -517,7 +517,7 @@ static void block_insert(oparg_T *oap, char_u *s, int b_insert, struct block_def
if (has_mbyte && spaces > 0) {
int off;
- // Avoid starting halfway a multi-byte character.
+ // Avoid starting halfway through a multi-byte character.
if (b_insert) {
off = (*mb_head_off)(oldp, oldp + offset + spaces);
} else {