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,410 public repositories matching this topic...
-
Updated
Sep 30, 2020 - Python
-
Updated
Oct 6, 2020 - Emacs Lisp
-
Updated
Oct 6, 2020 - Vim script
-
Updated
Oct 6, 2020 - Vim script
-
Updated
Oct 6, 2020 - JavaScript
-
Updated
Oct 4, 2020 - Vim script
-
Updated
Apr 1, 2020 - TypeScript
-
Updated
Oct 6, 2020 - Vim script
-
Updated
Oct 3, 2020 - C
-
Updated
Oct 4, 2020 - Python
Describe the feature
There should be an easier way to open latex-preview-pane-mode
when in LaTeX mode than using M-x
then searching for it.
System information
((system (type . gnu/linux) (config . "x86_64-pc-linux-gnu") (shell . "/usr/bin/zsh") (uname . "Linux 5.4.0-48-generic #52-Ubuntu SMP Thu Sep 10 10:58:49 UTC 2020 x86_64") (path "~/.nvm/version
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
Oct 4, 2020 - C++
-
Updated
Oct 6, 2020 - Python
Title says it all: I'm not sure how to escape special characters in my vimwiki text. In particular, I have a note where I want to use an asterisk to refer to a "footnote" at the bottom of the note.
I realize there is probably a better way to express a footnote, but that would still leave the question of how to put, e.g., a literal asterisk in the text for any other (valid) reason.
Thanks!
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