-
-
Notifications
You must be signed in to change notification settings - Fork 10
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
Python smartparens Fix #10
Python smartparens Fix #10
Conversation
Thanks for the fix! I have opened another PR at #10. I think this should be the correct fix and your PR definitely gives me the hint about the conflict. Thanks for spending time on this! :D |
Cool 🙂 , I've pulled and python + smartparens works. I see that |
Since we have function
Ah, yes. You are correct. I have tried with Edit: Ah, okay. I figured that I have |
I'm using master and the changes lgtm 👍 , shall I close this PR? |
Yes! Thanks for spending time looking into code for issue #5. :) |
No problem, thanks for your fast response 🙂 |
Hi 👋 I think this PR should fix #5 (at least the behaviour with python + smartparens).
What I think was happening was that if
docstr-trigger-python
detected the next three chars were"""
it would remove them and not call(docstr--insert-doc-string (docstr-python--parse))
by virtue of the if-then-else (I don't think behaviour is intended? - please correct me on this if it is).This path was always hit if smartparens mode was enabled since it inserts the three chars
"""
after the point once it detects three"""
in a row.Let me know if this fixes the issue ~ thanks Laurence