-
-
Notifications
You must be signed in to change notification settings - Fork 3
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
Does not support Pry.editor proc #4
Comments
Definitely interested. Out of curiosity, is there a reason you can't use a On Wed, Mar 6, 2013 at 8:05 PM, Felix Buenemann notifications@github.comwrote:
|
It's required so pry knows how to supply the line number, see this url for details: https://github.com/pry/pry/wiki/Editor-integration#wiki-Set_editor |
But right here is a very liberal regex that should correctly figure it out, no? |
Yes, you are right, that should be sufficient. I guess I looked at the documentation and not the source when I added that line to my .pryrc ;-) |
Btw. why not hook directly into pry to invoke the editor? That way the code would not be duplicated. There's a public method |
I'm not sure that that existed back when I first wrote pry-editline. But yeah, it sounds like the way to go (so long as irb compatibility is maintained). |
Ah, yes there's still people using that. I'll give it a shot. |
Btw. big ❤️ for all the great vim plugins! |
The code doesn't handle the code where Pry.editor is not a simple path but a proc, eg.:
The code should check if
editor.is_a? Proc
and then useeditor.call(filename, 1)
.I'll try to make a PR once I find some time.
(If anyone's curious, the above code focuses iTerm after closing MacVim started from Pry.)
The text was updated successfully, but these errors were encountered: