vim-sensible
ultisnips
Our great sponsors
vim-sensible | ultisnips | |
---|---|---|
27 | 64 | |
5,045 | 7,425 | |
- | - | |
0.0 | 4.9 | |
about 1 month ago | about 1 month ago | |
Vim Script | Python | |
- | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
vim-sensible
-
Obsidian 1.5 Desktop (Public)
That’s a good question. The built in tutorial is actually really good, you can launch it with “vimtutor” on the command line. It doesn’t give you everything, but its instructions and text to try things out on in the editor itself, which I find a good way to learn. It isn’t particularly programming focused either.
For getting used to the motions especially https://vim-adventures.com can be a fun way, in its game format.
For getting started I’d say don’t worry about plugins much, but get https://github.com/tpope/vim-sensible at least so the defaults meant for vi don’t get in the way. The only other thing you might want is a format syntax if your preferred note syntax isn’t highlighted well by default or something. Polyglot can be good to stave that off but really I’d say learn on a really lean config, and get used to using :help or similar. It’s the best way to learn the parts that work everywhere.
-
Share NO-PLUGIN Configs!
it's modified from tpope's https://github.com/tpope/vim-sensible, and https://github.com/mhinz/vim-galore#tips-1.
-
The Vim features that make me a Vim user instead of a Vi user
I didn't realise vim Vs vi purist was a thing.
I'm aware that for a while vim has had some backwards compatibility setting that people recommended turning off to get more modern defaults.
And that Tim Pope had a plugin that took you one step beyond that:
https://github.com/tpope/vim-sensible
> Think of sensible.vim as one step above 'nocompatible' mode: a universal set of defaults that (hopefully) everyone can agree on.
And that neovim took the opportunity to make an updated set of defaults:
https://neovim.io/doc/user/vim_diff.html#nvim-defaults
-
From vscode to vim
tpope/vim-sensible, because the Vim defaults aren't for everyone.
-
mini.basics - Common configuration presets for options/mappings/autocommands
A while back I did a public Neovim options survey (here are the results). One of the goals was to gather a commonly used option values to create a "crowd-sourced" moderate version of tpope/vim-sensible. Well, this is it.
-
How I set up Vim for writing LaTex, Python, C and C++?
opps.. forgot to mention timpopes : https://github.com/tpope/vim-sensible settings :D
-
Show HN: Vim online editor using WebAssembly, storing files using IndexedDB
You don’t want any modern conveniences? Not even stuff from here[0]?
[0]: https://github.com/tpope/vim-sensible/blob/master/plugin/sen...
-
How do you turn off the yellow highlighting after your done with the search?
If you use vim-sensible, which you should, you can reset the highlight with ctrl+l.
-
.vimrc
Check out sensible.vim for lots of settings you might want to turn on.
-
Neovim built-in options survey needs your contribution
What I plan to do with results: - The summary of results will be released in some way, shape, or form after survey is closed (at least two weeks from now when there is a 24 hours without new entries). It will be announced in this sub. - Possibly use the most commonly set non-default settings to power a Neovim variant, crowd-sourced version of tpope/vim-sensible.
ultisnips
-
LaTeX and Neovim for technical note-taking
I always like people's LaTeX-based note taking setups. I'm a mathematician, so I write a lot of LaTeX too. (And I use vim, so I really like vim+Latex workflows).
It's interesting that this post (or rather, the later post that discusses this) talks about the advantages of UltiSnips. The well-known vim-LaTeX posts written by Gilles Castel (RIP) relied pivotally on UltiSnips.
It's not just that UltiSnips is a snippet engine. There are many of those (including LuaSnip, the other snippet engine mentioned in the OP series of articles). It's that UltiSnips can dispatch arbitrary expressions to short python code sections, and python has a great scientific library. For example, it's trivial to write a `sympy` snippet that will simplify or compute a given expression and write the output in latex for you.
But UltiSnips works *terribly* with neovim [1] [2]. Why? Because UltiSnips uses python, and neovim's python interface is 100x slower than vim's python interface. There are design decisions for this and I'm not trying to say that neovim is bad. I use both vim and neovim. But I use vim+UltiSnips+vimtex for writing LaTeX.
LuaSnip has interpolation too. I suppose it would be possible to write more code that calls from LuaSnip to a system like sympy (or other). But that's work. On the other hand, I think it takes a true power user to actually want or use the fancy interpolation functions.
[1]: https://github.com/SirVer/ultisnips/issues/974
-
Looking for tutorials / Hello world projects to create Neovim plugins using Pynvim
I think in-the-wild examples like Ultisnips deoplete semshi (although they are advanced and somewhat complex) would also be good examples to learn how one can use python for writing plugins.
- UltiSnips – Snippet Solution for Vim
-
lsp-zero v2.x is now available
I didn't know lsp-zero, but this integration seems just for me except for that I am using UltiSnips instead of luasnip. Just curious how difficult do you think it is to add UltiSnips integration along with cmp-nvim-ultisnips?
- Minimalistic neovim/vim with batteries included ?
- How to solve this? (Ultisnippets plugin)
-
Awkwardness when typing in '\n' or '\t' or (...) [...] etc. -- (Have others noticed this too?) -- (is there a better way?)
If you use UltiSnips, you can just do this:
-
Vim + LaTeX
Snipets or code completion can be done in a number of different ways, and how that is configured will depend on what method you use. In the blog he uses the vim plugin ultisnips. You'll find details on configuration for that in that link.
-
Python36.dll not found
Heyo, I've been trying to get UltiSnips and YouCompleteMe to work, however, I've ran into a bit of a problem. The python36.dll library does not seem to exist for UltiSnips, and YouCompleteMe cannot locate python at all (screenshots at bottom).
- SirVer/ultisnips: UltiSnips - The ultimate snippet solution for Vim. Send pull requests to SirVer/ultisnips!
What are some alternatives?
vim-cool - A very simple plugin that makes hlsearch more useful.
LuaSnip - Snippet Engine for Neovim written in Lua.
lightline.vim - A light and configurable statusline/tabline plugin for Vim
vim-vsnip - Snippet plugin for vim/nvim that supports LSP/VSCode's snippet format.
goyo.vim - :tulip: Distraction-free writing in Vim
completion-nvim - A async completion framework aims to provide completion to neovim's built in LSP written in Lua
ale - Check syntax in Vim/Neovim asynchronously and fix files, with Language Server Protocol (LSP) support
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
vimrc - Basic vim configuration for your .vimrc
friendly-snippets - Set of preconfigured snippets for different languages.
vim-easy-align - :sunflower: A Vim alignment plugin
emmet-vim - emmet for vim: http://emmet.io/