-
Notifications
You must be signed in to change notification settings - Fork 51
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
What about e
to edit or o
to open
#30
Comments
@stoivo Great idea! |
This has been implemented with afe8327! It hasn't been released yet but I would love to get your feedback on the current implementation! |
It works when I have editor set to
|
@stoivo Hmmm I will look in to it. Thanks for the feedback though 👍 |
Still did work when set to
|
Oh I didn't realize the code breaks when you have a flag in the |
Great! Comment here when thats done and I will test it :D |
Not sure if this is the most elegant solution but 9c16b8a fixes the issue! Let me know if it works for ya :D |
Awesome, not it doesn't crash 💥
And thank you for doing all this for everyone! |
I will definitely look into that 👍
Hmm I can't re-create this on my side. Can I see your |
Check out this demo. |
Ah I see what you did. If you look at https://camo.githubusercontent.com/0178c2f554229485cbfd94e3439b4f27d093d2fe/68747470733a2f2f692e696d6775722e636f6d2f47734a4d5249702e676966, I made it so that the conflict markers must stay intact. If not, the prompt turns red, signing an error. This was because it would be less work by the user and also help them fix their mistakes by not making their action conclusive. What do you think? |
Clever, but unexpected. |
Good point. I'm thinking about putting comments like how It loooks like it will be implemented around next month golang/go#4896 |
What about
e
to edit oro
to open .In case I manually want to merge the conflict
The text was updated successfully, but these errors were encountered: