-
Notifications
You must be signed in to change notification settings - Fork 467
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
Two issues with python-mode
snippets
#490
Comments
I just had a look at the warning about the unknown directive "NOTE". That exact line has been in the snippet for 7 years so it must be something in yasnippet itself. Indeed, yasnippet commit joaotavora/yasnippet@25f5d88 (19 January) added the warning message for unknown directives. Removing the colon seems like a valid workaround, but of course a pull request to modify the snippet is better. |
About the message for the multiple snippets with the same identity, I see that message is added in yasnippet commit joaotavora/yasnippet@8e9ce76 (12 February). Looking at the code comment, it is allowed for one snippet to overwrite another one, but apparently this is not one of these cases. |
@JulienPalard Your commit 9f67370 adds Python snippet file The snippets are slightly different. Is there a need to support both but if not, which should be the one to keep? |
Thanks for reporting. I opened pr #500 to remove one of the two iter. I kept the one consistent with the other snippets. |
When I open a Python file, I get two yasnippet warnings. First:
function_docstring
has the following line in its header:Removing the colon (or the entire "NOTE: " part) solves the issue.
Second:
There are two snippets for
__iter__
, one in a file callediter
and one in a file called__iter__
. Unfortunately, both use__iter__
for thename:
directive. Since both snippets essentially do the same thing, perhaps one can be removed?I know these are minor issues, but the warnings are displayed in the echo area and may push out other, more important, warnings. (Such as an issue with Eglot, in my case...)
The text was updated successfully, but these errors were encountered: