You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What I have noticed under GNU/Linux (Ubuntu 12.04 LTS 64bit) using Emacs 24.3.1 is that the helm interface freezes for a small break (about a second on my machine/Internet connection) after I have typed something but before any options show up in the search results.
I would expect that the Emacs interface would remain responsive while the search is performed and the output prepared.
This renders the interface still usable, but far from ideal as it pauses just enough to make it difficult to type.
Reproduction is easy for me. This happens every time I search for something on with helm-spotify.
If I were to guess what is happening, I would say that either helm is blocking all input while the web API request is made, request received, parsed, and the helm list is populated. I assume that this is not a slowness in Helm itself (this is my first time using helm) or the parsing, but rather simply the web API taking some time.
Perhaps an idle timer would fix things?
P.S. this is a pretty awesome toy.
The text was updated successfully, but these errors were encountered:
Hmm...this might be possible to improve. Both helm and the built-in url package support asynchronous operation, but in different ways that aren't straightforwardly compatible. I'll have to figure out how to wire them together. It sees like it'll be an interesting couple of things to learn, so I'll see what I can do when I get some time. But that probably won't be until next week...
What I have noticed under GNU/Linux (Ubuntu 12.04 LTS 64bit) using Emacs 24.3.1 is that the helm interface freezes for a small break (about a second on my machine/Internet connection) after I have typed something but before any options show up in the search results.
I would expect that the Emacs interface would remain responsive while the search is performed and the output prepared.
This renders the interface still usable, but far from ideal as it pauses just enough to make it difficult to type.
Reproduction is easy for me. This happens every time I search for something on with helm-spotify.
If I were to guess what is happening, I would say that either helm is blocking all input while the web API request is made, request received, parsed, and the helm list is populated. I assume that this is not a slowness in Helm itself (this is my first time using helm) or the parsing, but rather simply the web API taking some time.
Perhaps an idle timer would fix things?
P.S. this is a pretty awesome toy.
The text was updated successfully, but these errors were encountered: