Issue #247 resolved

evil-invert-char should respect evil-cross-lines

Lintaro INA
created an issue

Currently, ~ does not cross lines even if evil-cross-lines is t.

My understanding is that evil-cross-lines corresponds to Vim's whichwrap=b,s,h,l,<,>,[,] option and makes everything except ~ cross lines. Shouldn't this also be applied to ~ so that evil-cross-lines corresponds to whichwrap=b,s,h,l,<,>,[,],~?

Comments (3)

  1. Frank Fischer repo owner
    • changed status to open

    Hm, I've not even been aware of the whichwrap option, so I would say it's more or less a coincidence that the current behaviour corresponds to setting whichwrap=b,s,h,l,<,>,[,]. But I agree that it makes sense to let ~ wrap as well.

  2. Frank Fischer repo owner

    allow evil-invert-char crossing lines (fix #247)

    If evil-cross-lines and evil-move-cursor-back are non-nil then executing evil-invert-char usually bound to ~ should move point to the first character on the next line.

    → <<cset 1fc4c237d65c>>

  3. Frank Fischer repo owner

    allow evil-invert-char crossing lines (fix #247)

    If evil-cross-lines and evil-move-cursor-back are non-nil then executing evil-invert-char usually bound to ~ should move point to the first character on the next line.

    → <<cset 1fc4c237d65c>>

  4. Log in to comment