Skip to content
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

:r after :m doesn't work as expected #1313

Closed
brianhuffman opened this issue Dec 10, 2021 · 2 comments · Fixed by #1319
Closed

:r after :m doesn't work as expected #1313

brianhuffman opened this issue Dec 10, 2021 · 2 comments · Fixed by #1319
Labels
UX Issues related to the user experience (e.g., improved error messages)

Comments

@brianhuffman
Copy link
Contributor

brianhuffman commented Dec 10, 2021

If I load a module by filename with :l, and it fails due to a parsing/typechecking error, then I can edit the file and type :r to try loading it again.

However, if I load the error-containing module by module name with :m, and I try to do the same thing, it doesn't work: Instead, it just reloads whatever module (if any) was loaded before I typed the :m command. If only the cryptol prelude was loaded before the :m command, then :r does nothing at all.

I would expect the two module-loading commands (:l and :m) to work consistently in connection with :r.

@brianhuffman brianhuffman added the UX Issues related to the user experience (e.g., improved error messages) label Dec 10, 2021
yav added a commit that referenced this issue Jan 13, 2022
@yav
Copy link
Member

yav commented Jan 13, 2022

@brianhuffman I think #1319 should fix this, have a look.

@brianhuffman
Copy link
Contributor Author

I tried it out, and it seems to work as expected. Thanks @yav!

yav added a commit that referenced this issue Feb 7, 2022
@yav yav closed this as completed in #1319 Feb 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
UX Issues related to the user experience (e.g., improved error messages)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants