Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

differences from neosnippet #365

Closed
nhooyr opened this issue Jan 4, 2017 · 9 comments
Closed

differences from neosnippet #365

nhooyr opened this issue Jan 4, 2017 · 9 comments

Comments

@nhooyr
Copy link

nhooyr commented Jan 4, 2017

What makes this plugin different from ultisnips? They both seem really similar.

@Shougo
Copy link
Owner

Shougo commented Jan 4, 2017

Multiple post:
SirVer/ultisnips#807

Do you think both seem similar?
No.

neosnippet is Vim script based plugin.
UltiSnips is if_python based plugin.

neosnippet uses snipMate based snippet syntax.
UltiSnips uses the original syntax.

UltiSnips users can embed Python code in the snippet syntax.

neosnippet uses the jump marker. It cannot support backward jump.
UltiSnips does not use the marker. But it must detect the buffer change.
It will be slower.

@Shougo Shougo closed this as completed Jan 4, 2017
@nhooyr
Copy link
Author

nhooyr commented Jan 4, 2017

I wanted both perspectives is all :)

thanks!

@Shougo
Copy link
Owner

Shougo commented Jan 4, 2017

UltiSnips is slow in neovim.
Because, neovim if_python implementation is slow.

Note: I will rewrite neosnippet in the future.
https://github.com/Shougo/deoppet.nvim

@lfilho
Copy link

lfilho commented May 12, 2017

Ooh, I came here research about which snippet engine to use with nvim (i've been using snipmate so far). Nice. So I guess I should wait for deoppet? Or does neosnippet works well with nvim?

Also, if you don't mind answering some more questions:

  1. Why don't you use the snippets at https://github.com/honza/vim-snippets since they also have the snipmate format?
  2. When do you think deoppet will be usable?

THANKS again for your great effort with some many nice plugins! You rock!

@Shougo
Copy link
Owner

Shougo commented May 15, 2017

Or does neosnippet works well with nvim?

neosnippet works well with nvim.

So I guess I should wait for deoppet?

It takes more time. I am busy to fix the plugin bugs.

When do you think deoppet will be usable?

I think it is in 2018.

Why don't you use the snippets at https://github.com/honza/vim-snippets since they also have the snipmate format?

Because I like neosnippet-snippets.

gurpreetatwal added a commit to gurpreetatwal/dotfiles that referenced this issue Jul 30, 2018
Compared snipmate, ultisnips and neosnippet

snipmate lacked many features and seemed inferiror to ultisnips
neosnippet might be faster but was also lacking in many features
- see  Shougo/neosnippet.vim#365

features of ultisnips I liked:
 - preserves tabstops when going in/out of normal/insert mode
 - visual block selection
 - auto reloading of snippets

 might be worth looking at deoppet.nvim when it comes out
@svanharmelen
Copy link

I just noticed this thread and the link to deoppet. Can you share any updates on when you think deoppet will be stable and can be used? Thanks!

@Shougo
Copy link
Owner

Shougo commented Sep 17, 2018

I just noticed this thread and the link to deoppet. Can you share any updates on when you think deoppet will be stable and can be used? Thanks!

It is in 2019 someday. Because In 2018 is defx.nvim development turn.

@Shougo
Copy link
Owner

Shougo commented Sep 17, 2018

I think it is in 2018.

The plan is changed...

And deoppet.nvim is neovim only plugin.

@svanharmelen
Copy link

Check! And I'm using neovim, so that's all good 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants