search

withfig / fig

Public issue tracker for Fig.
https://fig.io
MIT License
2.06k stars 63 forks source link

Typing feels sluggish / slow #1268

Open clo4 opened 2 years ago

clo4 commented 2 years ago

Some people have reported that typing feels slow. We can't reproduce this (it's just as fast for us!) but if you can, please get in touch! We'd love to see a video of this so we can dive in deeper.

JasperSui commented 2 years ago

It feels sticky when you type some commands and you delete them char by char, it will try to search any possible keywords even if the deletion is not completed yet.

I understand it will take some time to display all possibilities when you are typing, but it's annoying when I try to fix a part of the command I just typed.

My laptop spec: Mac OS X, Monterey Apple silicon (M1 Chip) iTerm2 zim + zsh + powerlevel10k

Hope it helps.

batwolf commented 2 years ago

For me, typing is sticky.

I've taken a video recording of some strange things.

I'm in my terminal, I start typing: git push. When I get as far as git pu the autocomplete starts to kick in, showing push as an option, so I hit enter, and I end up with git puspush

If i try it again, it works normally, but going to a new line reproduces this.

In general, typing is laggy, and I've had a few instances where I've had to wait at least a second for the terminal to respond. I cannot reproduce this, but I do know that this did not happen before I installed Fig.

briancarlson commented 2 years ago

As soon as i start fig and begin typing there is severe input lag. Video with activity monitor disabled/enabled. https://share.getcloudapp.com/2NuzLzbr 2019 mbp/32g ram, iterm2, zsh

clo4 commented 2 years ago

@briancarlson this is very interesting!! Thank you for the video - just connected some dots that narrow down this problem a lot.

I created #1479 not long ago which is an easy repro of this same problem. AFAIK the whole team uses iTerm, so we could all repro. After seeing your video I tested this, this only happens while Fig.app is running. If you run yes in any other terminal, or run it in iTerm without Fig running, everything is as snappy as expected.

So this is only an issue with iTerm while the Fig app is open. Very weird!

@grant0417 this might be an issue with figterm but I'm actually leaning more towards it being a weird interaction with the Mac app.