-
-
Notifications
You must be signed in to change notification settings - Fork 554
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
Fish importing #234
Fish importing #234
Conversation
set up fish init script
IMHO, keybinds should not a default setting |
This is currently the standard behaviour of all of the shell integrations, I don't think we should handle fish any differently |
Co-authored-by: PJ <me@panekj.dev>
Co-authored-by: PJ <me@panekj.dev>
Co-authored-by: PJ <me@panekj.dev>
Co-authored-by: PJ <me@panekj.dev>
Also missing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Amaaazing, thanks @conradludgate!
And thanks @panekj for your help too 😊 Really happy to get this issue closed off, I'll release it soon
So happy to see it ❤️, Thank you @conradludgate. I can't wait to see the next release ! |
Closes #57
So, Fish YAML is not real YAML. So there's no point bringing out a YAML parser for this. Instead, we read line by line.
We use
-
at the beginning to determine whether the line is a new entry. If we find a new entry line and we've found acmd: ...
value, we exit the loop and return our history item.It's pretty fault tolerant, ignoring bad lines and missing values.