Skip to content

scenario where ghost memory is annoying #188

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

Open
disconcision opened this issue Mar 23, 2025 · 1 comment
Open

scenario where ghost memory is annoying #188

disconcision opened this issue Mar 23, 2025 · 1 comment

Comments

@disconcision
Copy link
Member

not a bug, but an interesting scenario several participants encountered.

Starting from this state:

Image

what we want to do is move the parentheses over and replace the arrow with the comma (we want to do a few other things too but those aren't relevant here):

Image

it feels perfectly reasonable to approach this from left to right; that is, insert the comma:

Image

then delete the paren and the arrow:

Image

this leaves this awkward tween state that people hated; the paren remembering its position stops the grout on either side from merging.

If you just go put the closing parens where you want it, it all gets cleaned up, but the tween state distracts people.

deleting the arrow, inserting the comma, and then deleting the parens works better, but feels less natural:

Image
@disconcision
Copy link
Member Author

Dupe of #160

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