{"action":"created","issue":{"url":"https://api.github.com/repos/neovim/neovim/issues/1820","labels_url":"https://api.github.com/repos/neovim/neovim/issues/1820/labels{/name}","comments_url":"https://api.github.com/repos/neovim/neovim/issues/1820/comments","events_url":"https://api.github.com/repos/neovim/neovim/issues/1820/events","html_url":"https://github.com/neovim/neovim/pull/1820","id":54505472,"number":1820,"title":"[WIP] Reimplement builtin terminal UI using libtermkey/unibilium","user":{"login":"tarruda","id":842846,"avatar_url":"https://avatars.githubusercontent.com/u/842846?v=3","gravatar_id":"","url":"https://api.github.com/users/tarruda","html_url":"https://github.com/tarruda","followers_url":"https://api.github.com/users/tarruda/followers","following_url":"https://api.github.com/users/tarruda/following{/other_user}","gists_url":"https://api.github.com/users/tarruda/gists{/gist_id}","starred_url":"https://api.github.com/users/tarruda/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tarruda/subscriptions","organizations_url":"https://api.github.com/users/tarruda/orgs","repos_url":"https://api.github.com/users/tarruda/repos","events_url":"https://api.github.com/users/tarruda/events{/privacy}","received_events_url":"https://api.github.com/users/tarruda/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/neovim/neovim/labels/refactor","name":"refactor","color":"bfe5bf"},{"url":"https://api.github.com/repos/neovim/neovim/labels/terminal","name":"terminal","color":"c7def8"},{"url":"https://api.github.com/repos/neovim/neovim/labels/WIP","name":"WIP","color":"ededed"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":128,"created_at":"2015-01-15T21:17:49Z","updated_at":"2015-02-05T15:15:12Z","closed_at":null,"pull_request":{"url":"https://api.github.com/repos/neovim/neovim/pulls/1820","html_url":"https://github.com/neovim/neovim/pull/1820","diff_url":"https://github.com/neovim/neovim/pull/1820.diff","patch_url":"https://github.com/neovim/neovim/pull/1820.patch"},"body":"This PR will throw a lot of old code into the garbage can."},"comment":{"url":"https://api.github.com/repos/neovim/neovim/issues/comments/73062368","html_url":"https://github.com/neovim/neovim/pull/1820#issuecomment-73062368","issue_url":"https://api.github.com/repos/neovim/neovim/issues/1820","id":73062368,"user":{"login":"elmart","id":135757,"avatar_url":"https://avatars.githubusercontent.com/u/135757?v=3","gravatar_id":"","url":"https://api.github.com/users/elmart","html_url":"https://github.com/elmart","followers_url":"https://api.github.com/users/elmart/followers","following_url":"https://api.github.com/users/elmart/following{/other_user}","gists_url":"https://api.github.com/users/elmart/gists{/gist_id}","starred_url":"https://api.github.com/users/elmart/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/elmart/subscriptions","organizations_url":"https://api.github.com/users/elmart/orgs","repos_url":"https://api.github.com/users/elmart/repos","events_url":"https://api.github.com/users/elmart/events{/privacy}","received_events_url":"https://api.github.com/users/elmart/received_events","type":"User","site_admin":false},"created_at":"2015-02-05T15:15:12Z","updated_at":"2015-02-05T15:15:12Z","body":"> Can you post the input_enqueue log of <c-o> only?\r\n\r\nWell, the point is that nothing appears in the log when I press `<C-O>`. That's why I said it gets \"swallowed\". Is there a more basic point, before `input_enqueue`, that I can log at? Before, it was `key_event`, but I don't see it anymore.\r\n\r\n> function key parsing should be fixed now\r\n\r\nF4 mappings work now, but not completely. I still have the issue about quickly repeated mappings described in a [former](https://github.com/neovim/neovim/pull/1820#issuecomment-71260209) post.\r\nThe following corresponds to 9 quickly repeated F4 + j. As you see, they are delivered ok to nvim:\r\n```\r\n2015/02/05 16:05:12 [error @ input_enqueue:159] 78170 - keys: {.data = [<F4>], .size = [5]}\r\n2015/02/05 16:05:12 [error @ input_enqueue:159] 78170 - keys: {.data = [j], .size = [1]}\r\n2015/02/05 16:05:13 [error @ input_enqueue:159] 78170 - keys: {.data = [<F4>], .size = [5]}\r\n2015/02/05 16:05:13 [error @ input_enqueue:159] 78170 - keys: {.data = [j], .size = [1]}\r\n2015/02/05 16:05:13 [error @ input_enqueue:159] 78170 - keys: {.data = [<F4>], .size = [5]}\r\n2015/02/05 16:05:13 [error @ input_enqueue:159] 78170 - keys: {.data = [j], .size = [1]}\r\n2015/02/05 16:05:13 [error @ input_enqueue:159] 78170 - keys: {.data = [<F4>], .size = [5]}\r\n2015/02/05 16:05:13 [error @ input_enqueue:159] 78170 - keys: {.data = [j], .size = [1]}\r\n2015/02/05 16:05:13 [error @ input_enqueue:159] 78170 - keys: {.data = [<F4>], .size = [5]}\r\n2015/02/05 16:05:13 [error @ input_enqueue:159] 78170 - keys: {.data = [j], .size = [1]}\r\n2015/02/05 16:05:13 [error @ input_enqueue:159] 78170 - keys: {.data = [<F4>], .size = [5]}\r\n2015/02/05 16:05:13 [error @ input_enqueue:159] 78170 - keys: {.data = [j], .size = [1]}\r\n2015/02/05 16:05:13 [error @ input_enqueue:159] 78170 - keys: {.data = [<F4>], .size = [5]}\r\n2015/02/05 16:05:13 [error @ input_enqueue:159] 78170 - keys: {.data = [j], .size = [1]}\r\n2015/02/05 16:05:13 [error @ input_enqueue:159] 78170 - keys: {.data = [<F4>], .size = [5]}\r\n2015/02/05 16:05:13 [error @ input_enqueue:159] 78170 - keys: {.data = [j], .size = [1]}\r\n2015/02/05 16:05:14 [error @ input_enqueue:159] 78170 - keys: {.data = [<F4>], .size = [5]}\r\n2015/02/05 16:05:14 [error @ input_enqueue:159] 78170 - keys: {.data = [j], .size = [1]}\r\n``` \r\nbut somehow, they get interpreted some other way. The first F4 + j does what it should, but the following ones produce a `^G` in the screen, that dissapear on the next keystroke, and then produce the effect of a single `j` (line down). In fact, if I do the same while in insert mode (to see interpreted keystrokes, as the mapping for `<F4>j` is only for normal mode) then I get the following:\r\n```\r\n<F4>j<2-F4>j<3-F4>j<4-F4>j<F4>j<2-F4>j<3-F4>j<4-F4>j<F4>j<2-F4>j<3-F4>j<4-F4>j<F4>j<2-F4>j<3-F4>j<4-F4>j<F4>j<2-F4>j<3-F4>j<4-F4>j<F4>j<2-F4>j<3-F4>j\r\n```\r\nAs you can see, there's a strange cycle, where the first `<F4>j` gets interpreted as such, but the second one is interpreted as `<2-F4>j`, the third as `<3-F4>j`, and so on. I don't know what `<2-F4>` is supposed to mean. Note also that the cycle stops at 4 and the goes back to the beginning.\r\n\r\nI hope that makes sense. Please ask if I've not been clear on anything."}}