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

add snipmate settings #861

Merged
merged 1 commit into from Mar 11, 2021
Merged

add snipmate settings #861

merged 1 commit into from Mar 11, 2021

Conversation

joaomarcos96
Copy link
Contributor

There's this annoying message whenever I start vim:

$ vim ~/.zshrc
The legacy SnipMate parser is deprecated. Please see :h SnipMate-deprecate.
Press ENTER or type command to continue

This is because SnipMate's legacy version, as stated in :h SnipMate-deprecate:

The legacy parser, version 0, is deprecated. It is currently still the default
parser, but that will be changing. NOTE that switching which parser you use
could require changes to your snippets--see the previous section.

To continue using the old parser, set g:snipMate.snippet_version (see
SnipMate-options) to 0 in your vimrc.

Setting g:snipMate.snippet_version to either 0 or 1 will remove the start up
message. One way this can be done--to use the new parser--is as follows:

let g:snipMate = { 'snippet_version' : 1 }

This PR proposes a SnipMate settings file, in which the snippet version is set explicitly in order to remove the startup message. It is set to 0 as it's still the default version.

@jhon-tonet
Copy link

Works fine for me... Tks!

Copy link

@colinschoen colinschoen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we merge this

@lfilho lfilho merged commit 4f444cb into skwp:master Mar 11, 2021
@lfilho
Copy link
Collaborator

lfilho commented Mar 11, 2021

Thanks!

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

Successfully merging this pull request may close these issues.

None yet

4 participants