Alexander-Miller
Alexander-Miller
Your use case is very similar to treemacs, where I did implement frame locality a while ago. If a simple one buffer per frame approach is what you're going for...
Any chance we can get this merged? I currently have a build failing only in CI, so I can really use some proper output now.
Sending emacs a SIGUSR2 will also show a backtrace of what its doing.
I dont do cider, but to me nothing in there looks suspicious. You can also try profiling your CPU with `profiler-start` & `profiler-report`.
I suppose you can try hooking up some of the expensive parts to `trace-function`, see how many times they're being called and with what values. Maybe theres room for improvement....
I haven't quite thought so far ahead, I had only starting groking how it works when I had the working version you see here. I'll take it into account for...
Updated what I think should be a working implementation. I am not quite happy with having to use a `catch`, but cannot think of a better option - doing a...
Got things clean up and documented now. There's quite a few changes to the .info file, probably due to the version difference, so I think you should regenerate the file...
Because I don't know the feature list all that well and was only looking at whatever what be useful with my own use-case :man_shrugging:. I've added the same options as...
> What do you think about also supporting inactive timestamps? Not something I want to get into in this PR (don't personally see much of a use-case either). But easy...