search

lastquestion / explain-pause-mode

top, but for Emacs.
GNU General Public License v3.0
241 stars 6 forks source link

Searching for Explanations of the Most Recent Pause #86

Open JiaHong-Lee opened 4 years ago

JiaHong-Lee commented 4 years ago

Hi, thank you for this great package.

I open this issue because I couldn't find any related previous discussion.

Previously, there are recent pause information echoes in the minibuffer. Also, the *explain-pause-top* was sorted in chronological order.

Now, using the latest commit 02961514aa1a102691be4ad5c0a90283920621ca, the *explain-pause-top* has become more informative, but how can I sort the explanation in reverse chronological order? Or maybe there is another way to get the most recent pause explanation?

This is desired because after experiencing a sudden pause, I want to find out causes of the pause.

lastquestion commented 4 years ago

Hi,

thanks for trying it out and using it!

You're right, there is no reverse chronological order. The pauses are shown in order per command, but you don't see the last pause highlighted in any way. And there's no way to tell which one of the slow ones was the last slowest.

I'm open to ideas about how to visualize this information.

Hm, I could order top by "last executed command`, but post-command hooks, self-insert-command, etc are very frequent, and quickly would push down whatever was slow. That could work if there was a filter option to "only show slow things".

Another option would be to show the last slowest thing and when it happened at the top of the buffer like an alert or header.

I kind of like that idea more; that would be a good call to action to another view or some kind of better reverse timeline view.

If you have other ideas, or prefer one or the other, please let me know.

ashiklom commented 4 years ago

I'm also interested in this feature, as I would like to use this library to diagnose a nasty and difficult-to-reproduce hang.

Hm, I could order top by "last executed command`, but post-command hooks, self-insert-command, etc are very frequent, and quickly would push down whatever was slow. That could work if there was a filter option to "only show slow things".

As long as this wasn't the default, I think this could actually be useful for a use case like mine where I am trying to diagnose a hang; it would at least give me a sense of the most recent functions called before Emacs ground to a halt.