Anything look slow in this rofi blezz timing profile?

[focusaurus]

Here's a gist with the profile timings and the command line I use. Starting a new discussion from this comment in a thread about leaving the rofi window running long term.

I've never read one of these before but I think it's pretty much done in about 275ms which is not slow, but I can realistically type 2 keystrokes faster than that and have the second one still grabbed by the previous application.

The longest time between 2 logs I think is here:

(process:185580): Timings-DEBUG: 15:05:57.342: 0.096727 (0.000015): source/view.c:rofi_view_repaint:286 flush
(process:185580): Timings-DEBUG: 15:05:57.522: 0.276428 (0.179701): source/view.c:rofi_view_refilter_real:1170 Filter start

[DaveDavenport]

It looks like that is when it start responding to your input, as it refilters the list.

From this point on it should be taking your keyboard input, and it should not land in any other application anymore:
(process:185580): Timings-DEBUG: 15:05:57.271: 0.024924 (0.000007): source/rofi.c:startup:728 Grab keyboard

That is 24 ms.

How do you launch rofi? (what hotkey tool?)

[focusaurus]

I am running awesomewm and have a key mapped in my lua code to awful.spawn.easy_async(home_bin .. '/blezz', noop) which runs my blezz script which is in the gist.

[DaveDavenport]

hmm I have very little experience with awesomewm. maybe if I have some time I can take a look. (but won't be soon, as I have negative time to spend on rofi).

[focusaurus]

Don't worry about it.

[focusaurus]

Gonna hard code user id instead of running id -u and see if that helps.