{"action":"created","issue":{"url":"https://api.github.com/repos/guns/vim-sexp/issues/9","labels_url":"https://api.github.com/repos/guns/vim-sexp/issues/9/labels{/name}","comments_url":"https://api.github.com/repos/guns/vim-sexp/issues/9/comments","events_url":"https://api.github.com/repos/guns/vim-sexp/issues/9/events","html_url":"https://github.com/guns/vim-sexp/issues/9","id":59699167,"number":9,"title":"visual mode mappings are created indiscriminately","user":{"login":"justinmk","id":1359421,"avatar_url":"https://avatars.githubusercontent.com/u/1359421?v=3","gravatar_id":"","url":"https://api.github.com/users/justinmk","html_url":"https://github.com/justinmk","followers_url":"https://api.github.com/users/justinmk/followers","following_url":"https://api.github.com/users/justinmk/following{/other_user}","gists_url":"https://api.github.com/users/justinmk/gists{/gist_id}","starred_url":"https://api.github.com/users/justinmk/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/justinmk/subscriptions","organizations_url":"https://api.github.com/users/justinmk/orgs","repos_url":"https://api.github.com/users/justinmk/repos","events_url":"https://api.github.com/users/justinmk/events{/privacy}","received_events_url":"https://api.github.com/users/justinmk/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2015-03-03T20:18:21Z","updated_at":"2015-03-04T01:31:17Z","closed_at":"2015-03-03T22:16:25Z","body":"Many of the default `g:sexp_mappings` do not make sense in visual mode (correct me if I'm wrong). To avoid visual-mode mappings, extra configuration steps are needed.\r\n\r\nIf I configure sexp mappings like this:\r\n\r\n```\r\nlet g:sexp_mappings = { 'sexp_insert_at_list_head': '<I' }\r\n```\r\n\r\nvim-sexp creates `nmap` and `xmap` mappings, but `sexp_insert_at_list_head` is not really useful in visual-mode. \r\n\r\nIn order to avoid this, I must do this:\r\n\r\n```\r\nnmap <I     <Plug>(sexp_insert_at_list_head)\r\nlet g:sexp_mappings = { 'sexp_insert_at_list_head': '' }\r\n```\r\n\r\nPerhaps the plugin could be more discriminating about which maps it creates in visual-mode. "},"comment":{"url":"https://api.github.com/repos/guns/vim-sexp/issues/comments/77080072","html_url":"https://github.com/guns/vim-sexp/issues/9#issuecomment-77080072","issue_url":"https://api.github.com/repos/guns/vim-sexp/issues/9","id":77080072,"user":{"login":"guns","id":55776,"avatar_url":"https://avatars.githubusercontent.com/u/55776?v=3","gravatar_id":"","url":"https://api.github.com/users/guns","html_url":"https://github.com/guns","followers_url":"https://api.github.com/users/guns/followers","following_url":"https://api.github.com/users/guns/following{/other_user}","gists_url":"https://api.github.com/users/guns/gists{/gist_id}","starred_url":"https://api.github.com/users/guns/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/guns/subscriptions","organizations_url":"https://api.github.com/users/guns/orgs","repos_url":"https://api.github.com/users/guns/repos","events_url":"https://api.github.com/users/guns/events{/privacy}","received_events_url":"https://api.github.com/users/guns/received_events","type":"User","site_admin":false},"created_at":"2015-03-04T01:31:17Z","updated_at":"2015-03-04T01:31:17Z","body":"> It is not traditional for Vim operations\r\n\r\nYes, this is true. I'm not actually a very traditional Vimmer, so this doesn't\r\nbother me too much. I totally understand how it might feel irksome to others,\r\nthough.\r\n\r\nIn light of this, I've added documentation on replacing the whole\r\n`g:sexp_mappings` system with a standard autocmd approach:\r\n\r\nhttps://github.com/guns/vim-sexp/blob/b4398689f7483b01684044ab6b55bf369744c9b3/doc/vim-sexp.txt#L460-L589\r\n\r\nThis isn't news to you, of course, but it does list all the mappings created\r\nby vim-sexp in a convenient, copy-pastable format. I suspect you may prefer to\r\nhandle the mappings this way.\r\n\r\nI promise never to break backwards compatibility without at least a ~year of\r\ndeprecation notice.\r\n\r\nThanks again for reporting!\r\n"}}