{"action":"created","issue":{"url":"https://api.github.com/repos/radare/radare2/issues/7130","repository_url":"https://api.github.com/repos/radare/radare2","labels_url":"https://api.github.com/repos/radare/radare2/issues/7130/labels{/name}","comments_url":"https://api.github.com/repos/radare/radare2/issues/7130/comments","events_url":"https://api.github.com/repos/radare/radare2/issues/7130/events","html_url":"https://github.com/radare/radare2/issues/7130","id":216950818,"number":7130,"title":"reverse-i-search does not allow editing the found item before evaluation","user":{"login":"ewtoombs","id":2224848,"avatar_url":"https://avatars0.githubusercontent.com/u/2224848?v=3","gravatar_id":"","url":"https://api.github.com/users/ewtoombs","html_url":"https://github.com/ewtoombs","followers_url":"https://api.github.com/users/ewtoombs/followers","following_url":"https://api.github.com/users/ewtoombs/following{/other_user}","gists_url":"https://api.github.com/users/ewtoombs/gists{/gist_id}","starred_url":"https://api.github.com/users/ewtoombs/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ewtoombs/subscriptions","organizations_url":"https://api.github.com/users/ewtoombs/orgs","repos_url":"https://api.github.com/users/ewtoombs/repos","events_url":"https://api.github.com/users/ewtoombs/events{/privacy}","received_events_url":"https://api.github.com/users/ewtoombs/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2017-03-25T05:16:25Z","updated_at":"2017-03-25T10:11:24Z","closed_at":null,"body":"A history item found with ctrl-r can't be edited after it is found. The only way I've found to do so is to run the command as-is, then edit it after. I must say that's no ideal.\r\n\r\nIdeally, after having found the history item you're looking for, hitting escape, ctrl-J, or the arrow keys should cancel the reverse-i-search and return to the regular line editing mode with the most recently found history item in the line buffer. This is how it works in bash, zsh, and the python shell, and is what I've come to expect of REPLs."},"comment":{"url":"https://api.github.com/repos/radare/radare2/issues/comments/289202359","html_url":"https://github.com/radare/radare2/issues/7130#issuecomment-289202359","issue_url":"https://api.github.com/repos/radare/radare2/issues/7130","id":289202359,"user":{"login":"radare","id":917142,"avatar_url":"https://avatars2.githubusercontent.com/u/917142?v=3","gravatar_id":"","url":"https://api.github.com/users/radare","html_url":"https://github.com/radare","followers_url":"https://api.github.com/users/radare/followers","following_url":"https://api.github.com/users/radare/following{/other_user}","gists_url":"https://api.github.com/users/radare/gists{/gist_id}","starred_url":"https://api.github.com/users/radare/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/radare/subscriptions","organizations_url":"https://api.github.com/users/radare/orgs","repos_url":"https://api.github.com/users/radare/repos","events_url":"https://api.github.com/users/radare/events{/privacy}","received_events_url":"https://api.github.com/users/radare/received_events","type":"User","site_admin":false},"created_at":"2017-03-25T10:11:24Z","updated_at":"2017-03-25T10:11:24Z","body":"I will enhance this reverse mode with this but  there are different ways to use the shell, i implemented the ones i use and the ones i expect, happy to learn some new ones, do you plan to fix this? Theres a commit from this week implementing the ^a/^e thing that you can take as an example.\n\nIf not ill do when i find some spare time\n\n> On 25 Mar 2017, at 06:16, ewtoombs <notifications@github.com> wrote:\n> \n> A history item found with ctrl-r can't be edited after it is found. The only way I've found to do so is to run the command as-is, then edit it after. I must say that's no ideal.\n> \n> Ideally, after having found the history item you're looking for, hitting escape, ctrl-J, or the arrow keys should cancel the reverse-i-search and return to the regular line editing mode with the most recently found history item in the line buffer. This is how it works in bash, zsh, and the python shell, and is what I've come to expect of REPLs.\n> \n> —\n> You are receiving this because you are subscribed to this thread.\n> Reply to this email directly, view it on GitHub, or mute the thread.\n> \n"}}
{"actor":{"display_login":"radare"}}