@mattly I’ve never seen that before. If you can debug that to determine where it’s coming from that would be useful. You can try disabling just proto repl to see if that’s really the cause.

hm. well, how reliable is Timecop?

so, this is interesting; on my work machine, timecop reports proto-repl taking 12151ms to "activate"; on my personal machine, 747ms

the config on my personal machine isn't as fleshed out yet, so it might have something to do with other packages

but that time does really seem to inform the time between "Open..." and being able to use the window