Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Possibly this is a bug, but I'm not sure. Through user fow in #vim on freenode, I've confirmed no side effect in 7.3.409, but there is a side effect in 7.3.547 (the version on my computer.)

The easiest way to test is to copy paste the following file into a vim buffer, jump to the beginning (gg) and follow the instructions.

Hi there, this is a test case.
This line is short.

After opening this file issue the following commands:
$j:set cuc<Enter>k

You'll notice that the cursor should be on the period after "case" this is expected behavior.

Next enter the following commands:
:set nocuc<Enter>$hj:set cuc<Enter>k

You'll notice that the cursor should now be on the word "a" rather than on the "e" at the end of "case"

So when you have a column value (not end of line) then :set cuc modifies this value as a sideeffect.

Is there anyway to workaround this issue? Is this a bug? Can anyone else reproduce?

share|improve this question

migrated from Mar 18 '13 at 8:46

This question came from our site for professional and enthusiast programmers.

I confirm your observation in 7.3.854. You should try the vim-dev mailing list. And I don't think this question is suitable for SO. – romainl Mar 18 '13 at 6:26

You must log in to answer this question.

Browse other questions tagged .