Win.printr is called too much about lf HOT 3 CLOSED

@KenjiTakahashi For command completion it should be necessary since the completion window could have been narrowed down in the second time and the text there need to be redrawn. We can buffer the text that goes there though in order to get rid of filtering each time which is most likely the bottleneck there. Still ~5 second sounds quite annoying even if it is only when navigating. I hope #14 can help here.

For quitting it shouldn't be necessary.

I will prioritize adding the profiling to the code so we can do better than blind optimization.

from lf.

Yeah, #14 helps here. Still it's strange to have to wait for redraw when you want to close the app anyway ;-).

Profiling sounds good 👍.

from lf.

With commit 6094078 previews are now buffered and Win.printr is a cheap operation. Hence I'm closing this issue now. The rest is tracked in #5.

from lf.