{"action":"created","issue":{"url":"https://api.github.com/repos/emacs-helm/helm/issues/1568","repository_url":"https://api.github.com/repos/emacs-helm/helm","labels_url":"https://api.github.com/repos/emacs-helm/helm/issues/1568/labels{/name}","comments_url":"https://api.github.com/repos/emacs-helm/helm/issues/1568/comments","events_url":"https://api.github.com/repos/emacs-helm/helm/issues/1568/events","html_url":"https://github.com/emacs-helm/helm/issues/1568","id":166136310,"number":1568,"title":"Follow on typing","user":{"login":"quicknir","id":10457096,"avatar_url":"https://avatars.githubusercontent.com/u/10457096?v=3","gravatar_id":"","url":"https://api.github.com/users/quicknir","html_url":"https://github.com/quicknir","followers_url":"https://api.github.com/users/quicknir/followers","following_url":"https://api.github.com/users/quicknir/following{/other_user}","gists_url":"https://api.github.com/users/quicknir/gists{/gist_id}","starred_url":"https://api.github.com/users/quicknir/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/quicknir/subscriptions","organizations_url":"https://api.github.com/users/quicknir/orgs","repos_url":"https://api.github.com/users/quicknir/repos","events_url":"https://api.github.com/users/quicknir/events{/privacy}","received_events_url":"https://api.github.com/users/quicknir/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2016-07-18T16:30:53Z","updated_at":"2016-07-18T16:49:57Z","closed_at":null,"body":"Right now, it seems like follow mode in helm only launches the persistent action when you press down or up. What would be nice is if the persistent action also launched whenever text was typed in, causing the results to be updated; currently after a query completes the cursor is on the first hit but the buffer has not actually jumped to it, which seems inconsistent. Following on update leads to a nice flow where one uses typing to narrow down results and examines if the desired point has been reached on the buffer, instead of needing the arrow keys at all. I tried doing this on my own for helm-ag via\r\n\r\n```\r\n(add-hook 'helm-after-update-hook 'helm-execute-persistent-action)\r\n``` \r\n\r\nHowever, the perfomance was rather poor. Is it possible to make this more efficiently, either non-intrusively in user code, or perhaps by changing slightly how follow mode works inside helm itself?"},"comment":{"url":"https://api.github.com/repos/emacs-helm/helm/issues/comments/233387665","html_url":"https://github.com/emacs-helm/helm/issues/1568#issuecomment-233387665","issue_url":"https://api.github.com/repos/emacs-helm/helm/issues/1568","id":233387665,"user":{"login":"quicknir","id":10457096,"avatar_url":"https://avatars.githubusercontent.com/u/10457096?v=3","gravatar_id":"","url":"https://api.github.com/users/quicknir","html_url":"https://github.com/quicknir","followers_url":"https://api.github.com/users/quicknir/followers","following_url":"https://api.github.com/users/quicknir/following{/other_user}","gists_url":"https://api.github.com/users/quicknir/gists{/gist_id}","starred_url":"https://api.github.com/users/quicknir/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/quicknir/subscriptions","organizations_url":"https://api.github.com/users/quicknir/orgs","repos_url":"https://api.github.com/users/quicknir/repos","events_url":"https://api.github.com/users/quicknir/events{/privacy}","received_events_url":"https://api.github.com/users/quicknir/received_events","type":"User","site_admin":false},"created_at":"2016-07-18T16:49:57Z","updated_at":"2016-07-18T16:49:57Z","body":"One thing I have tried is messing with helm input idle delay. Setting that high enough eliminates the lag, but it also makes the text less responsive. I think a way to solve this would be to provide a hook that runs after update, but with its own, customizable delay. In other words, a hook that runs its functions after update is complete and e.g. 0.2 seconds has gone by, but if another update comes along before that time has expired, then the hook just doesn't run. That way the text feedback can feel fast and smooth, and it can jump to the first hit quite snappily as well."}}
{"actor":{"display_login":"quicknir"}}