{"action":"created","issue":{"url":"https://api.github.com/repos/jcfaria/Vim-R-plugin/issues/191","labels_url":"https://api.github.com/repos/jcfaria/Vim-R-plugin/issues/191/labels{/name}","comments_url":"https://api.github.com/repos/jcfaria/Vim-R-plugin/issues/191/comments","events_url":"https://api.github.com/repos/jcfaria/Vim-R-plugin/issues/191/events","html_url":"https://github.com/jcfaria/Vim-R-plugin/issues/191","id":118344740,"number":191,"title":"tmux settings have changed","user":{"login":"protist","id":646668,"avatar_url":"https://avatars.githubusercontent.com/u/646668?v=3","gravatar_id":"","url":"https://api.github.com/users/protist","html_url":"https://github.com/protist","followers_url":"https://api.github.com/users/protist/followers","following_url":"https://api.github.com/users/protist/following{/other_user}","gists_url":"https://api.github.com/users/protist/gists{/gist_id}","starred_url":"https://api.github.com/users/protist/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/protist/subscriptions","organizations_url":"https://api.github.com/users/protist/orgs","repos_url":"https://api.github.com/users/protist/repos","events_url":"https://api.github.com/users/protist/events{/privacy}","received_events_url":"https://api.github.com/users/protist/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":11,"created_at":"2015-11-23T09:29:00Z","updated_at":"2015-11-29T22:40:15Z","closed_at":"2015-11-23T10:15:27Z","body":"vim-r's help suggests the following in `~/.tmux`:\r\n```\r\nset -g mode-mouse on\r\nset -g mouse-select-pane on\r\nset -g mouse-resize-pane on\r\n```\r\nHowever, this fails with an error in the [latest tmux 2.1-1](https://stackoverflow.com/questions/11832199/tmux-set-g-mouse-mode-on-doesnt-work). These settings have been removed in tmux, and replaced with the following.\r\n```\r\nset -g mouse on\r\n```\r\nvim-r's help should be updated to reflect this."},"comment":{"url":"https://api.github.com/repos/jcfaria/Vim-R-plugin/issues/comments/160478533","html_url":"https://github.com/jcfaria/Vim-R-plugin/issues/191#issuecomment-160478533","issue_url":"https://api.github.com/repos/jcfaria/Vim-R-plugin/issues/191","id":160478533,"user":{"login":"protist","id":646668,"avatar_url":"https://avatars.githubusercontent.com/u/646668?v=3","gravatar_id":"","url":"https://api.github.com/users/protist","html_url":"https://github.com/protist","followers_url":"https://api.github.com/users/protist/followers","following_url":"https://api.github.com/users/protist/following{/other_user}","gists_url":"https://api.github.com/users/protist/gists{/gist_id}","starred_url":"https://api.github.com/users/protist/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/protist/subscriptions","organizations_url":"https://api.github.com/users/protist/orgs","repos_url":"https://api.github.com/users/protist/repos","events_url":"https://api.github.com/users/protist/events{/privacy}","received_events_url":"https://api.github.com/users/protist/received_events","type":"User","site_admin":false},"created_at":"2015-11-29T22:40:15Z","updated_at":"2015-11-29T22:40:15Z","body":"I spent a little while on this, but can't work it out. (It's academic for me anyway, since I'd prefer running vim-r from within tmux.) FWIW here is what I tried, but I've given up trying to reproduce it.\r\n\r\n`opencmd` looked similar in both installs, although it only executed fine in the clean Virtualbox environment. On my normal system, I tried executing the command itself (i.e. everything past the `-x` flag in `terminator`), which opened up the tmux session perfectly. Hence, it only seems to choke when opening a new terminator session.\r\n\r\nSimilarly, if I quit terminator, and run vim-r in konsole, it will launch terminator fine. It seems to be the presence of an existing terminator instance that causes it to choke. In the clean Virtualbox instance, it opens up a new instance fine.\r\n\r\nI thought perhaps my terminator config was to blame somehow, so I copied it to my clean Virtualbox install. However, even with this, the first test worked fine.\r\n\r\nAnyway, as I say, this bug doesn't directly affect me, so I've given up trying to isolate it. If you have a specific test, then I'm happy to try it, but otherwise this can stay closed. Thanks for your help."}}