• 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

• I have read through the manual page (man fzf)
• I have the latest version of fzf
• I have searched through the existing issues

Info

• OS
  • Linux
  • Mac OS X
  • Windows
  • Etc.
• Shell
  • bash
  • zsh
  • fish

Problem / Steps to reproduce

When supplying colored input to 'fzf --ansi', the highlighted entr

Issue Prelude

Please complete these steps and check these boxes (by putting an x inside
the brackets) before filing your issue:

• I have read and understood YCM's [CONTRIBUTING][cont] document.
• I have read and understood YCM's [CODE_OF_CONDUCT][code] document.
• I have read and understood YCM's [README][readme], **especially the
  [Frequently Asked Questions][faq]

this command in the installation section for macOS, but the option isn't found when running it

Describe the bug
Reading from stdin (i.e. vim -) causes vim to mark the buffer as modified. This prevents a user from quitting with :q, and instead must resort to :q!. This behavior runs contrary to what is documented under :h --, which states that "The buffer will not be marked as modified, so that it's easy to exit".

~This also prevents vim from opening to stdin in readonly mode,

Reference:
https://github.com/syl20bnr/spacemacs/blob/master/doc/DOCUMENTATION.org#replacing-text-with-iedit

In spacemacs, you cant delimiter the area of action of iedit, its super useful when you dont want to change every match on the file.

Environment

• Operating System: macOS Mojave Version 10.14.4
• Vim version :version: VIM - Vi IMproved 8.1 macOS version
• NERDTree version git rev-parse --short HEAD: f4d2b30
• NERDTree settings applied in your vimrc, if any:

" map toggle N

Running :GoDoc makes my vim session block as it is not ran in the background. This might not be an issue for small codebases, where the blocking call is quick enough, but it causes frustration when using the command on larger codebases.

It would be great if :GoDoc runs in the background, without blocking my editor, similar to how the guru-related commands work (e.g. :GoReferrers)

New Theme?

We would love to support all code editors out there, but we need your help to accomplish that. Feel free to create a new theme based on our color palette.

^^ Not a code editor, but a wayland launcher application

Documentation for wofi config

![screenshot](https://user-images.

Looking for help from the community regarding this issue.

Issue:
Sporadic CI failures.

Expected behavior:
Consistent CI results.

Actual behavior:
CI test may fail or pass with a rerun and no other change.

Steps to reproduce:
Run CI repeatedly by opening a PR and re-pushing minor changes until reproduced.

Reference issue: https://travis-ci.org/onivim/oni/jobs/4999

Neither here nor powerline/fonts has any documentation of what codepoints are supposed to be provided with which glyphs by fonts. This makes it virtually impossible for font authors to add support.

Also, I’ve seen you use the PUA. Please register your codepoints with http://www.evertype.com/standards/csur/ so they don’t overlap with any other CSUR PUA assignments. (It’s easy, I got a couple ass

Name: doc8
URL: https://github.com/PyCQA/doc8

It's a rst linter, i tried it in vscode and it w

Ranger may be implementing this already, in which case a link to the documentation place would be appreciated.

Given that ranger starts a "preview process", pass keys, or commands, from ranger to the preview process, mangling them if necessary, and update the preview.

the main use case would be scrolling the preview, eg control (or alt) + arrows would be passed as arrows to the preview proce

Seeing marks, ideally in the gutter, but maybe as a highlight or something, would be helpful. This apparently existed at one point (https://github.com/vscodevim/Vim//commit/713f30a1a8f4923dfc2e7b0cbceffce78ab83c01#diff-a7723f32fe6b05e135838f84e5c23c0fR870), but decoration options have gotten richer and we can put it under a setting.

Maybe the spelling check for English is heavily needed, and later support for Chinese?
Or is any workaround to do spelling check in vnote?

Thanks!

Describe the bug
When the bottom scrollbar is toggled off. It is not possible to make a window that is as tall as the available screen real estate. You can't drag (expand) the bottom edge of the window to the bottom of the screen. If you drag the whole window down such that the bottom edge is aligned with the bottom of the screen you can't drag the top edge to expand to meet the top of the sc

Currently, although the individual commands can have documentation, the only information about the mode itself is relegated its name. Something really cool would be if instead of a static string, kakoune could allow the mode to specify a command to be called for its docstring. This would allow kak-lsp to print the results of lsp-code-actions or lsp-hover above the list of subcommands.

As Doom continues to grow, so have incoming bug reports for modules I do not use and toolchains I know little about, like :lang clojure or :tools ein, and so I struggle to support them.

If you know a little nix and use Doom, consider contributing a shell.nix file to the module(s) you use the most. Particularly :lang modules, so that I can get a test environment up and running to test ag

Coming from Vimium, one feature I often lack is visual-line mode, which is typically more convenient when copying big chunks of text/code from the browser. Any chance shift+v will be introduced into qutebrowser?

Expected behavior:

When opening a preview with `p

I created a simple responsive page for the tutorial at https://github.com/mattn/emmet-vim/blob/master/TUTORIAL.

I made it with a style resembling the https://emmet.io/ website in case @mattn might want to use it on that site. After finishing I found that there's already an official doc with a more in-depth explanation at https://docs.emmet.io/.

So, anyway here's the [repo](https://github.co

I want to add the screenshots in README.
If you have good screenshots for deoplete README, can you add it in this issue?