Vim

Vim is a highly customizable text editor that can run in a shell. Bram Moolenaar is credited with the development of Vim, which he began in 1988.
Here are 8,567 public repositories matching this topic...
-
Updated
Nov 2, 2020 - Python
-
Updated
Nov 8, 2020 - Emacs Lisp
-
Updated
Nov 8, 2020 - Vim script
-
Updated
Oct 14, 2020 - Vim script
-
Updated
Nov 8, 2020 - JavaScript
-
Updated
Nov 8, 2020 - Vim script
-
Updated
Apr 1, 2020 - TypeScript
-
Updated
Nov 8, 2020 - Vim script
-
Updated
Nov 8, 2020 - C
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
-
Updated
Nov 8, 2020 - Python
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.
-
Updated
Nov 9, 2020 - C++
-
Updated
Nov 9, 2020 - Python
Prior to submitting a new issue make sure to complete these steps:
"# Generated
Ultisnips plays very good with for selection but w
Created by Bram Moolenaar
Released November 2, 1991
- Repository
- vim/vim
- Website
- www.vim.org/download.php
- Wikipedia
- Wikipedia
Actual behaviour
When simply trying to edit some additional files I often type
:e *.js
or something similar; this almost ALWAYS results inE77: Too many file names
.Expected behaviour
It's pretty clear what the user wants in this situation; they want to open the files as buffers! I'm sure there are legacy reasons for this error, but it's a pretty poor experience these days that