thoughtbot / dotfiles

A set of vim, zsh, git, and tmux configuration files.
https://thoughtbot.com
Other
7.97k stars 1.87k forks source link

Unable to change windows - fresh install #460

Closed noctrnal closed 8 years ago

noctrnal commented 8 years ago

Fresh install of thoughtbot/laptop and thoughtbot/dotfiles. When I have 2 vertical splits in vim, everything is superb. When I open a third, I cannot change windows to the new window.

If remove .vim/ and .vimrc, functionality is restored.

I have also tried multiple rcups to see if that remedied the issue to no avail.

noctrnal commented 8 years ago

Seems to work if I VS from the left-most window. Bugs otherwise.

geoffharcourt commented 8 years ago

Hi @noctrnal, what version of Vim are you using? Are you using tmux? What OS (assuming you're in OS X if you used Laptop)?

noctrnal commented 8 years ago

Using Vim version 7.4.944, not using tmux, and running El Capitan.

geoffharcourt commented 8 years ago

@noctrnal does this happen with only thoughtbot/dotfiles in place with none of your own customizations? I took a peek at your dotfiles and it looks like you have some of your own Vim configuration that might be relevant.

noctrnal commented 8 years ago

Happening with only thoughtbot/laptop and thoughtbot/dotfiles in place. The dotfiles on my github is not being used as the thoughtbot versions is about the best thing I've found. I've used these in previous dev environments without this problem. Possibly related to el capitan?

geoffharcourt commented 8 years ago

@noctrnal sorry for all the questions, but this is an odd behavior from your editor. Which shortcut are you using to switch panes? Can you paste in the output from :map for that key-combination?

noctrnal commented 8 years ago

No worries at all. I'm a big fan of the TB dotfiles, so glad to provide the additional information.

I'm using control + w + h|j|k|l to switch panes. Although double tapping control + w produces same bug when opening a new pane from anything other than the far left pane.

Wasn't sure how to get a :map for those specific commands so pasted whole output in ss's:

screen shot 2015-12-10 at 12 58 38 pm screen shot 2015-12-10 at 12 56 43 pm screen shot 2015-12-10 at 12 55 51 pm

noctrnal commented 8 years ago

I've tried removing .vim/ and .vimrc, verifying that the problem does not persist, reinstalling dotfiles, and confirming problem again crops up.

geoffharcourt commented 8 years ago

I don't see anything there that looks suspicious, but can you paste the output of :map <C-w>? There's some results off the screen, and I just want to be sure we're not missing anything.

geoffharcourt commented 8 years ago

Also, is this Terminal.app or iTerm 1/2?

noctrnal commented 8 years ago

iTerm 2, build 2.1.4.

:map <C-w> showing 'No mapping found'. Strange, can definitely control + w between panes until opening a new vertical split pane from a non-left-most pane.

geoffharcourt commented 8 years ago

The <C-w> shortcuts you're using are built in to Vim, so they don't show up as mapped commands unless you've overridden them. I'll give this some more thought.

geoffharcourt commented 8 years ago

@noctrnal I've been unable to recreate this in Vim 7.4.963 or Neovim. Could you update Vim to that patch and try once more?

noctrnal commented 8 years ago

Upgraded Vim but went to 7.4.1016 in the upgrade. Same problem exists after reinstall. Should I try Vim 7.4.963?

geoffharcourt commented 8 years ago

@noctrnal, no need to downgrade. At this point I'm not sure how to troubleshoot this beyond commenting out the entirety of .vimrc and then re-enabling it a line or chunk at a time until you identify the offending code. If you can figure out what setting breaks it on your machine we'll have a better place to start work on a fix.

noctrnal commented 8 years ago

Have not had a chance to go through .vimrc to find which line(s) are griefing me, but I'm not seeing the same problem with Neovim.

geoffharcourt commented 8 years ago

Hi @noctrnal, since we can't reproduce this on a bare Vim 7.4 or Neovim build, I suspect this is something going on with your personal configuration (maybe in your terminal?).

I'm going to close the issue, but if you isolate a particular line that's the cause, please reopen this issue and we can discuss.