• nvim --version: NVIM v0.4.3
• vim -u DEFAULTS (version: ) behaves differently?
• Operating system/version: MacOS
• Terminal name/version:
• $TERM: xterm-256color

Steps to reproduce using nvim -u NORC

Suppose there are two files test.vim and test2.vim in the same directory:

test.vim

let id1 =

• Category
  • fzf binary
  • fzf-tmux script
  • Key bindings
  • Completion
  • Vim
  • Neovim
  • Etc.
• OS
  • Linux
  • Mac OS X
  • Windows
  • Windows Subsystem for Linux
  • Etc.
• Shell
  • bash
  • zsh
  • fish

If my SHELL variable points to a

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]

Although a lot of useful keys are mentioned in documentation it would be really handy to have some official document solely dedicated to various shortcuts in spacemacs.

Other thing which I miss even more is that there is to my knowledge no list of free to assign keys, so that users at the moment need to double check the

Is your feature request related something that is currently hard to do? Please describe.
Entering special characters in a terminal window (:terminal) is not straightforward. They can be copy-pasted from elsewhere but this is not convenient.

Describe the solution you'd like
In a terminal window, digraphs could be entered with CTRL-K, just like in a normal window. For example, doing

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.

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)

Looking for help from the community regarding this issue.

Issue:
Unclear CI test failure.

Expected behavior:
Failed test would indicate the failure with some extra info for investigation.

Actual behavior:
Prints Expected: true, Actual: false which is less than optimal.

Steps to reproduce:
Run a failing test.

Would help to have more verbose logging for the tests

https://github.com/LeCoupa/awesome-cheatsheets/blob/master/backend/node.js#L77 should be more like

const foo = require('./subfolder/foo.js')
console.log('foo "%s"', foo) // "foo"

// now grab the "module" wrapper around './foo.js'
const fooModule = require.cache[require.resolve('./subfolder/foo.js')]

console.log('foo module', fooModule)
// load module ./bar relative to ./foo
//

The install instructions on draculatheme.com/jetbrains are outdated, referencing a non-existing Dracula.icls file. However, the README.md file in the jetbrains-master download describes an installation using a new plugin that works nicely.

Have you considered automatically generating the instructions on draculatheme.com based on the README.md file (or another file) that is part of this repo

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

Describe the bug
When I grab multiple lines of text in visual mode and click S, it is expected that it deletes all lines that are selected and puts me into insert mode. But what is happening instead is that it puts me into insert mode and allows me to insert one character at the start and beginning of the selection.

To Reproduce
Steps to reproduce the behavior:

1. Open the file

OS Version (操作系统): Windows, Linux

VNote Version (Help - About VNote - Version: )(VNote版本): 2.2(Windows), 2.5(Linux), 2.6(Linux)

Symptoms (表现):
Mermaid Gantt 导出的 HTML 图表显示为空白
HTML 源代码中 元素的 translate 横坐标和 width 出现不正确的负数数值，代码如下

<g class="grid" transform="translate(75, 266)">
            <g class="tick" transform="translate(-19,0)" style="opacity: 1;">
                <line y

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.

Maybe I just missed it, but it seems that :search-next and :search-prev always wrap around at the moment.
Would it be possible to add a boolean argument to these commands to control whether search wraps around ?

This is not an issue, but a feature request.
I have tried to somehow get a simple function to return true or false whether a jump is present
or not, but I couldn't get a reliable solution, that worked in every situation. Would it be possible
to implement a function "isJumpable" to do just that?

coc-snippets for example provides coc#jumpable() but I don't want to use coc-snippets with ultisni

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

if I understood it corretly from README.MD, we can install like this:

$ git clone https://github.com/donnemartin/dev-setup.git && cd dev-setup
$ ./.dots bootstrap osxprep brew osx

and later when we need datastores, we run

$ cd ~/dev-setup
$ ./.dots datastores

I understand that bootstrap copies the dot files to the home directory, such as .bash_profile and .exports.
but

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