search

mtth / cursorcross.vim

Sane cursorcolumn and cursorline handling
33 stars 1 forks source link

doc: Reason for "enable cursorcolumn if at beginning of line else deactivate"? #1

Closed blueyed closed 10 years ago

blueyed commented 10 years ago

What is the idea behind having the cursorcolumn only in the first column?

edit I see now, it ignores any padding, which is indeed useful, to see where the indent lines up with. Still, it would be nice, if it would not interfere with existing mappings for CR/BS.

This feature also appears to be the only reason to map CR and BS in insert mode, which is inconvenient, because it may be mapped already, and cursorcross does not allow for remapping nor forwards the key.

mtth commented 10 years ago

Hey @blueyed You got it, the idea is to guide indentation. I'm open to suggestions if there are other ways to achieve this other than remapping <cr> and <bs> (to be exhaustive, we'd actually also have to remap <c-u>, <c-w>, etc. but the two previous probably cover 90%+ of all uses). As you mention, binding keys in insert mode seems to be hardly ever done which is why the mapping default to the usual saner noremap. If you have another usage for this mapping, I'd be happy to change it to map.

blueyed commented 10 years ago

A simple s/noremap/map/ will not suffice, especially since this would result in an infinite loop.

It is more about keeping/forwarding any existing map, which I have done locally.

Also, I have just provided a pull request for the endwise plugin - which should not overwrite the mapping from cursorcross: https://github.com/tpope/vim-endwise/pull/47

mtth commented 10 years ago

Thanks for the endwise change!