As I suggested in a comment here, I think it makes sense to map the operator mode for columnmove directly to the block wise modes, in order to be able to do deletes and replaces along the columns.

It is very simple to do this with custom mappings, as I've done (see here). However, I think this feature could be added as an optional feature.

If I do a columnwise motion delete, e.g. with d<c-v><m-f>c from the cursor at the first a in the following example:

aaa
bbb
ccc

And then repeat with dot ., then the plugin echoes call columnmove#ftFT_executer(). This happens with default settings.

Hello there. With the "spoiled" rule, (let g:columnmove_strict_wbege = 0), I would like to ask, what is difference between columnmove-w,b,e,ge and columnmove-W,B,E,gE ?

From the documentation, it seems that these are the same, since columnmove-w and its variants now only check based on empty spaces; it now does not check based on keywords.

Currently these mappings regard spaces and non-character positions as identical and never stop the cursor on a space. However I felt the behavior inconvenient sometimes. For example:

first line
second line
third line


sixth line

eighth line
ninth line

Thinking on a buffer like this, fourth fifth seventh lines are empty, when the cursor is in the sixth column columnmove-w does not stop the cursor at the sixth line, but I want it to stop actually!

So my idea is the cursor should be stopped even on a space if it is adjacent with non-character position. Basically these mappings work almost as same as before but the cursor stops slightly more frequent. I plan to merge the change soon and, probably, I will also implement an option to keep old behavior. Thanks.

Suppose I have the following text

{i}ndent0 i[n]dent0
  indent1 indent1
  indent1 indent1

  indent1
  indent1
  indent1
indent0

and the following settings

let g:columnmove_strict_wbege = 0 
let g:columnmove_stop_on_space = 1

With my cursor on [],
<M-e> moves the cursor to the space on line 3. This is the expected behavior, since g:columnmove_stop_on_space = 1.

Now, with my cursor on {},
<M-e> also takes me to line 3.
However, I hope that <M-e> moves the cursor to the second indent 0 on line 8.
That is, I wish to treat leading spaces in the same way as blank lines.

Would it be possible to add an option for this? Maybe g:columnmove_stop_on_leading_space?

I was made aware of this plugin due to this question on vi.stackexchage.com. It seems like a very nice plugin!

When testing it, I noticed that the columnwise motions are wrong when there are multi byte characters (or something similar). That is:

aa|a
aaa

bbb
øbb

ccc
ccc

Let | denote where the cursor is (i.e. first line column two). Now do <m-w> twice. This should leave the cursor on the second column on the sixth line, but instead I end up at the first column. The reason is that ø is a multi byte character or something like that.