-
Notifications
You must be signed in to change notification settings - Fork 27
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
Tab completion with export
causes panic
#286
Comments
Hi @iandwelker Looks like the bug is in the part that is supposed to be capturing the errors gracefully 🤦 Fortunately it seems an easy fix and easy for me to add additional test cases around too. So I'll get on that shortly. Are you're able to share your environmental variables prior to running Lastly I think it's worth noting that you might have uncovered two bugs: the panic you posted above, but also |
Output of
This also led me to realize another thing: the error only appears when I am running |
Hi @iandwelker Looks like it's the following env var that's triggering the bug:
If truth be told, I've never seen a multi line environmental variable before. Anyhow, I've completely rewritten how env vars are parsed (it was a lazy regex hack -- now I'm doing proper string parsing) and written a boat load of tests. I'm reasonably confident I've fixed the issue and since it's a pretty safe change I'll push it through to I'll also kick off the automated build process to generate new binaries. The new version number is |
Yeah, that's the only one I've ever seen as well. Thanks for getting that fixed up! And I do appreciate the lack of tab completion when typing in the name of the variable to export. However, this also disables directory tab completion when you're trying to export a directory as an environment variable. E.g. if you've typed Also, as a sidenote, would you be open to documentation PRs? I've noticed some areas that I think could be a bit better documented (no offense intended; this is a massive project so I wouldn't expect every tiny detail to be covered), and would love to file some PRs to improve documentation in those areas. |
It was but that can be changed. I've raise an issue: #288
Oh yes please!!! :D I'd very much welcome any contributions. |
My personal preference would be to have autocompletion when a variable's value is being set to a directory. However, that's just a personal preference, and could cause issues if someone's actually trying to insert a tab into a variable value, so (unless you have a strong opinion on the matter) the best option may be to just make it user-configurable?
Cool cool, I've forked the repo and I hope to submit a PR/some PRs soon :) |
It's very easy to add support for directories in addition to other fields. That code has already been written. What hasn't been written is support to load new tab completion rules upon a As for tabs, that could just be escaped:
Awesome, thank you. I should warn you that documentation is compiled in murex from
|
If
export
is typed as the base command, typing a space + any number of characters and then hitting tab will cause a panic. The panic message is:This occurs regardless of how much you have typed after
export
. It may be related to #135, but I don't know for certain. If you think it's related, I can close this issue and move the information over to the other issue.I'm seeing this on murex version 1.6.5100 BETA, macOS Big Sur 11.1. Let me know if there's more information you need from me.
The text was updated successfully, but these errors were encountered: