Suggestion: make g:CommandTMatchWindowReverse default to 1

[lencioni]

The reverse option is great because it puts the best suggestion close to where you are typing, and it is in a fixed location. This prevents your eyes from having to bounce around as you use Command-T. In observing people who have set up Command-T, I found that most just use the default order, which unnecessarily slows them down while working. I think that due to its better ergonomics and the low likelihood that people will discover and change the default that this option should be defaulted to 1. What do you think?

[wincent]

I agree that this option is an improvement (I've been using it myself ever since it was added, back in April 2011 in commit 3724567 [proof]), and I actually thought about piling together all the potential breaking changes — including toggling this default — in one fell swoop in the 2.0 release. At least some of the Command-T settings in my dotfiles are, by definition, settings that I would consider to be reasonable defaults for most people.

Trouble is, though, the way the Vim plug-in ecosystem works is that most people are tracking the master branch at all times via a plug-in manager, and so the notion of "releases" is becoming less and less meaningful. It means that things like semver and even the very concept of "release notes" become less useful. As a result, I've always been very, very careful about preserving backwards compatibility.

At least for things like renamed or deleted functions I was able to add deprecation warnings in the 2.0 release (see commit afc9442), but I can't really do that for options whose defaults have changed. I may just need to bite the bullet at some point and make the breaking change anyway. For some users it will cause pain, for others, enlightenment, and for others still might just be a UX improvement that goes unnoticed.

[lencioni]

For some users it will cause pain, for others, enlightenment, and for others still might just be a UX improvement that goes unnoticed.

I believe that the number of users that this particular change will cause pain for is relatively low and the solution to the pain is relatively simple. In my mind, the benefit here definitely outweighs the downside, and the earlier you make this change, the more benefit it will have and the less pain it will cause.

[wincent]

All right, I pulled the trigger on the next branch.

[lencioni]

Awesome! Exciting times we live in.

[sophiebits]

This surprised me today (hadn't pulled in a while…) but I figured out what changed with a bisect. :)

[lencioni]

Sorry about the surprise @spicyj! I'm curious: did you stick with the new default?

[sophiebits]

I didn't, but I had a fixed height already set. Maybe one day I'll switch.