• nvim --version: NVIM v0.5.0-23-gafd576ee9
• vim -u DEFAULTS (version: ) behaves differently? yes
• Operating system/version: Ubuntu 18.0.4.1 via WSL
• Terminal name/version: conhost
• $TERM: xterm-256color

Steps to reproduce using nvim -u NORC

Download:
[neovim_enc_bug.txt](https://github.com/neovim/n

• Category
  • fzf binary
  • Key bindings
• Shell
  • bash
  • zsh
  • fish

Eg, I would like to have the second item highlighted on startup.

It would be nice to call fzf as in:

echo -e 'abc\ndef' | fzf --bind 'start:down'

For reference, this is the tool I'm develop

https://github.com/SpaceVim/SpaceVim/blob/master/autoload/SpaceVim/plugins/projectmanager.vim#L199

init.toml

project_rooter_patterns        = ["Pipfile", ".git/"]

for a setup like mine

project/.git
project/whatever/Pipfile
project/whatever/x.py

the root should be project/whatever instead of project.

• I have read through https://github.com/junegunn/fzf.vim/blob/master/README.md
• I have read through https://github.com/junegunn/fzf/blob/master/README-VIM.md
• I have read through the manual page of fzf (man fzf)
• I have searched through the existing issues

My colorscheme stops working in the preview window (show_documentation window for functions).

It works fine in my native nvim terminal:

I've

Everything works fine, but there may be some confusion if users choose the recommended universal-ctags which does not use the $HOME/.ctags for config. It might be a good idea to include a wiki page explaining that any extra configs should be kept in $HOME/.ctags.d/*.ctags - might save on reported issues.

Expected behavior

Disable an annoying clang-tidy warning on linux

Steps to reproduce

1. Create a source file containing strncpy()
2. Observe that neomake complains
3. There is no way to disable this warning globally

In this case I would need to pass --checks=-clang-analyzer-security.insecureAPI.DeprecatedOrUnsafeBufferHandling to clang-tidy

Adding this as args for the c ma

Expected Behavior

on nvim 0.3.8

Actual Behavior

on nyaovim
<img width="399" alt="螢幕快照 2019-07-13 上午6 12 52" src="https://user-images.githubusercontent.com/40805

Hi,

When I run my tests using the neovim strategy, it opens a new terminal but auto focus on the buffer. Then I have to press <C-o> to not close the buffer and go back to my split pane.

Is there a way to have it open but not switch my focus to the newly opened pane automatically?

As a user (not versed in vimscript), I can't figure out how to use this module: may I suggest that it could be used by many more people if there was a user guide, that starts with the most commonly used features?

For example, I had no idea of how to do completion in vim-lsp: the provided links are not clear.

Another example is warnings: they are active by default, but how to learn more about

the readme has very nice Usage instructions but does not mention the neovim_path setting name. This might avoid some confusion, see e.g. https://stackoverflow.com/q/51070854/

Difficulty doing initial setup of the plugin
3rd party description of setup steps:
https://atlas-vim.readthedocs.io/vim/plugged/vim-ctrlspace/README/

• convert to plugin vim docs?
• create wiki pages on this repo?

如果使用gvim --remote-tab-silent首次打开MD文件时（此时gvim会注册servername "GVIM"），似乎BufEnter状态无法正确识别，因此s:init_command()和s:MkdpAU()都不能正常执行，只有使用givm --remote-tab-silent再打开任意一个文件后，才正常。

我把BufEnter改为BufRead，问题消失。

function! s:init() abort
if g:mkdp_command_for_global
au BufEnter * :call s:MkdpAU()
else
au BufEnter *.{md,mkd,markdown,mdown,mkdn,mdwn} :call s:MkdpAU()
endif
if g:mkdp_auto_star

I want to preemptively start this thread to survey for suggestions. A cursory search lead me to this promising repository https://github.com/enigo-rs/enigo

Since closing the window is a common point of failure, that will be the focus for the first pass of testing as I learn how to use the library.

Components for testing:

• bridge
• editor
• renderer
• settings
• wind

Is it possible to provide some descriptions in the documentation about some of the global variables (such as g:asyncrun_silent)? It looks like there are quite a few of said variables, and only two appear in the documentation.

Personally, I'm very interested in what variables are available and how they are intended to be used.