wincent / command-t

⌨️ Fast file navigation for Neovim and Vim
BSD 2-Clause "Simplified" License
2.75k stars 320 forks source link

Bug: results panel stays visible after selecting an item #264

Closed rafaelrinaldi closed 2 years ago

rafaelrinaldi commented 7 years ago

For some reason Command-T is not closing the results panel after I select an item. It happens randomly but frequently enough to bother me a lot.

Any ideas on what can be causing this?

My settings:

$ nvim --version
NVIM v0.2.0-150-g33319b1b
Build type: RelWithDebInfo
Compilation: /usr/local/Homebrew/Library/Homebrew/shims/super/clang -Wconversion -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -O2 -g -DDISABLE_LOG -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wvla -fstack-protector-strong -fdiagnostics-color=auto -DINCLUDE_GENERATED_DECLARATIONS -DHAVE_CONFIG_H -I/tmp/neovim-20161221-52925-4fb5k5/build/config -I/tmp/neovim-20161221-52925-4fb5k5/src -I/usr/local/include -I/usr/local/include -I/usr/local/include -I/usr/local/include -I/usr/local/include -I/usr/local/include -I/usr/local/opt/gettext/include -I/usr/include -I/usr/include -I/tmp/neovim-20161221-52925-4fb5k5/build/src/nvim/auto -I/tmp/neovim-20161221-52925-4fb5k5/build/include
Compiled by tesla@pizza.local

Optional features included (+) or not (-): +acl   +iconv    +jemalloc +tui      
For differences from Vim, see :help vim-differences

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/usr/local/Cellar/neovim/HEAD-33319b1/share/nvim"

~ 
$ tmux -V
tmux 2.3

~
$ ruby -v
ruby 2.4.0p0 (2016-12-24 revision 57164) [x86_64-darwin16]

~
$ nvim +CheckHealth

health#deoplete#check
========================================================================
## deoplete.nvim
  - SUCCESS: has("nvim") was successful
  - SUCCESS: has("python3") was successful
  - INFO: If you're still having problems, try the following commands:
    $ export NVIM_PYTHON_LOG_FILE=/tmp/log
    $ export NVIM_PYTHON_LOG_LEVEL=DEBUG
    $ nvim
    $ cat /tmp/log_{PID}
    and then create an issue on github

health#nvim#check
========================================================================
## Configuration
  - SUCCESS: no issues found

## Performance
  - SUCCESS: Build type: RelWithDebInfo

## Remote Plugins
  - SUCCESS: Up to date

========================================================================
## Clipboard
  - SUCCESS: Clipboard tool found: pbcopy

## Python 2 provider
  - INFO: `g:python_host_prog` is not set.  Searching for python2 in the environment.
  - INFO: Executable: /usr/local/bin/python2
  - INFO: Python2 version: 2.7.13
  - INFO: python2-neovim version: 0.1.12
  - SUCCESS: Latest python2-neovim is installed: 0.1.12

## Python 3 provider
  - INFO: `g:python3_host_prog` is not set.  Searching for python3 in the environment.
  - INFO: Executable: /usr/local/bin/python3
  - INFO: Python3 version: 3.6.0
  - INFO: python3-neovim version: 0.1.12
  - SUCCESS: Latest python3-neovim is installed: 0.1.12

## Ruby provider
  - SUCCESS: Found up-to-date neovim RubyGem
  - INFO: Ruby Version: ruby 2.4.0p0 (2016-12-24 revision 57164) [x86_64-darwin16]
  - INFO: Host Executable: /usr/local/bin/neovim-ruby-host
  - INFO: Host Version: 0.3.1

Ps.: my gut feeling says it has something to do with tmux.

wincent commented 7 years ago

Interesting. I've never seen anything like this. Hard to know how to investigate this without having a reliable repro. If you can stomach using Vim outside of tmux for a while, you could test your intuition that it only happens inside tmux.

rafaelrinaldi commented 7 years ago

@wincent Yeah, will do that and then share the result here. Thanks!

rafaelrinaldi commented 7 years ago

@wincent Just tried it for a while and I can confirm that outside of tmux it works perfectly. Do you have any ideas on why I'm getting this weird behavior? Here's my tmux configuration file.

wincent commented 2 years ago

Given the big rewrite for v6.0.x, I'm closing all older issues as there is unlikely to be anything significant happening on the 5-x-devel branch from here on[^patches]. Feedback issue for 6.0.x is here:

[^patches]: Patches and PRs would be welcome, but my personal efforts are going to be directed towards main.