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

experience report: attempting first MVU task issues #73

Open
disconcision opened this issue Nov 7, 2024 · 0 comments
Open

experience report: attempting first MVU task issues #73

disconcision opened this issue Nov 7, 2024 · 0 comments

Comments

@disconcision
Copy link
Member

  1. starting from this state:
Screenshot 2024-11-07 at 3 06 19 PM

entering opening parens ends up with an extra space at the end:

Screenshot 2024-11-07 at 3 06 23 PM
  1. then from this state:
Screenshot 2024-11-07 at 3 06 47 PM

attempting tab completion yields a FailedToPerform (doesn't advance caret as before)

  1. then from this state:
Screenshot 2024-11-07 at 3 07 17 PM

pressing down key yields incorrect caret position:

Screenshot 2024-11-07 at 3 07 20 PM
  1. then from this state:
Screenshot 2024-11-07 at 3 13 17 PM

entering "|" somewhat unexpectedly puts the arrow on the next line:

Screenshot 2024-11-07 at 3 13 13 PM

and pressing backspace leaves the whole rule as a ghost:

Screenshot 2024-11-07 at 3 14 50 PM

if I start entering the pattern, the arrow then pops up to the current line:

Screenshot 2024-11-07 at 3 16 47 PM
  1. then from this state:
Screenshot 2024-11-07 at 3 19 34 PM

if I enter space and then "=" the following hole stays put, but if i just enter "=" with no preceeding space, the hole jumps up to the current line:

Screenshot 2024-11-07 at 3 17 39 PM
  1. and then completing the arrow by pressing ">" causes the subsequent rule indentation to change:
Screenshot 2024-11-07 at 3 21 34 PM
  1. and then from here:
Screenshot 2024-11-07 at 3 23 39 PM

inserting a wrapping parens inserts the closing on the next line, causing the "in" to move somewhat distractingly:

Screenshot 2024-11-07 at 3 23 41 PM
  1. and then from here
Screenshot 2024-11-07 at 3 24 55 PM

inserting an opening parens results in the closing ghost ending up outside? which i assume is a bug but am not totally sure:

Screenshot 2024-11-07 at 3 25 03 PM

anyway, most of these aren't egregious but things are going to add up... i feel that about ~20-40% of token boundary actions causes something slightly unexpected to happen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant