Skip to content

Snippets: env moved to be out-of-string, new variants, future import snips #68

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

Closed
wants to merge 1 commit into from

Conversation

ambv
Copy link

@ambv ambv commented Nov 22, 2016

Title says all.

Test plan: make test, passed. Installed locally, new snips work, env only
works outside of strings.

…snips

Title says all.

Test plan: `make test`, passed. Installed locally, new snips work, env only
works outside of strings.
@ambv
Copy link
Author

ambv commented Nov 22, 2016

Didn't bother to update the Sublime snippets as I saw they are already out-of-sync.

@ambv
Copy link
Author

ambv commented Nov 22, 2016

With this you can release :-)

@1st1
Copy link
Member

1st1 commented Nov 22, 2016

they are already out-of-sync.

So this PR syncs snippets with the official atom/language-python snippets?

@ambv
Copy link
Author

ambv commented Nov 22, 2016

No, I added a few that I was using in Vim. I see atom/language-python is what you had before. Would you like me to also submit those changes to atom/language-python?

@1st1
Copy link
Member

1st1 commented Nov 22, 2016

Would you like me to also submit those changes to atom/language-python?

Yes, I think the right way is to have them accepted there first. We try not to add features (besides better syntax highlighting) that aren't implemented in atom/sublime default packages.

@ambv
Copy link
Author

ambv commented Nov 22, 2016

I see, alright, might be sensible to add this info somewhere :-)

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.

2 participants