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

correcting case doesn't use existing arrow, #108

Open
disconcision opened this issue Feb 5, 2025 · 2 comments
Open

correcting case doesn't use existing arrow, #108

disconcision opened this issue Feb 5, 2025 · 2 comments
Labels
bug Something isn't working

Comments

@disconcision
Copy link
Member

after entering "cawe x" " "| x =>" i get:

Image

which is mostly expected, except for the space between the case and the x gets consumed (can file this individually if-desired; not sure what the status is now on space handling)

if i then try to correct by arrowing to the w, backspacing, arrowing to the end of the case, and entering space, i get:

Image

where i would expect it to use the existing arrow

@disconcision disconcision added the bug Something isn't working label Feb 5, 2025
@disconcision
Copy link
Member Author

disconcision commented Feb 5, 2025

Similarly; don't think this is a distinct issue, but not totally sure the space aspect is the same as it doesn't involve an expanding delimiter this time:

entering "set x = 7 in x" yields this:

Image

similarly, unexpected that it consumes the space between in and x

similarly, correcting by back arrowing, backspacing the s, entering l, arrowing to the end of the let and pressing space yields:

Image

@disconcision
Copy link
Member Author

Minified version of the space issue in the latter.

given:

Image

pressing space yields:

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant