{"action":"created","issue":{"url":"https://api.github.com/repos/Fuco1/smartparens/issues/446","labels_url":"https://api.github.com/repos/Fuco1/smartparens/issues/446/labels{/name}","comments_url":"https://api.github.com/repos/Fuco1/smartparens/issues/446/comments","events_url":"https://api.github.com/repos/Fuco1/smartparens/issues/446/events","html_url":"https://github.com/Fuco1/smartparens/issues/446","id":63766052,"number":446,"title":"Incorrect behaviour of `sp-...` nav commands when there's a paren inside a string","user":{"login":"vkz","id":917220,"avatar_url":"https://avatars.githubusercontent.com/u/917220?v=3","gravatar_id":"","url":"https://api.github.com/users/vkz","html_url":"https://github.com/vkz","followers_url":"https://api.github.com/users/vkz/followers","following_url":"https://api.github.com/users/vkz/following{/other_user}","gists_url":"https://api.github.com/users/vkz/gists{/gist_id}","starred_url":"https://api.github.com/users/vkz/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vkz/subscriptions","organizations_url":"https://api.github.com/users/vkz/orgs","repos_url":"https://api.github.com/users/vkz/repos","events_url":"https://api.github.com/users/vkz/events{/privacy}","received_events_url":"https://api.github.com/users/vkz/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/Fuco1/smartparens/labels/needs-verification","name":"needs-verification","color":"bfd4f2"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-03-23T16:27:21Z","updated_at":"2015-10-31T19:13:57Z","closed_at":null,"body":"This is likely to be related to this #367 issue, except I'm not using **evil**. \r\n\r\nProbably non-exhaustive list of faulty commands include:\r\n```elisp\r\nsp-up-sexp\r\nsp-beginning-of-sexp\r\nsp-end-of-sexp\r\n```\r\nand their **backwards** cousins.\r\n\r\nTrying one of the above commands on the following lines jumps to the outer most parens ignoring inner wrapped expressions, which is not at all the expected behaviour (point denoted with `|`):\r\n```elisp\r\n(define-key sp-keymap (kbd | \"C-(\") 'sp-down-sexp)\r\n(define-key sp-keymap (kbd | \"C-[\") 'sp-up-sexp)\r\n(define-key sp-keymap (kbd | \"C-{\") 'sp-beginning-of-next-sexp)\r\n```\r\n\r\nWith point inside string literals in the above expressions both `sp-beginning-of-sexp` and `sp-end-of-sexp` report **Unmatched expressions**.\r\n\r\nExperienced on:\r\n```\r\nGNU Emacs 24.4.1 (x86_64-apple-darwin14.0.0, NS apple-appkit-1343.16)\r\n of 2014-12-29 \r\n\r\nsmartparens-20150218.1058 freshly installed from elpa\r\n```"},"comment":{"url":"https://api.github.com/repos/Fuco1/smartparens/issues/comments/152764881","html_url":"https://github.com/Fuco1/smartparens/issues/446#issuecomment-152764881","issue_url":"https://api.github.com/repos/Fuco1/smartparens/issues/446","id":152764881,"user":{"login":"Fuco1","id":2664959,"avatar_url":"https://avatars.githubusercontent.com/u/2664959?v=3","gravatar_id":"","url":"https://api.github.com/users/Fuco1","html_url":"https://github.com/Fuco1","followers_url":"https://api.github.com/users/Fuco1/followers","following_url":"https://api.github.com/users/Fuco1/following{/other_user}","gists_url":"https://api.github.com/users/Fuco1/gists{/gist_id}","starred_url":"https://api.github.com/users/Fuco1/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Fuco1/subscriptions","organizations_url":"https://api.github.com/users/Fuco1/orgs","repos_url":"https://api.github.com/users/Fuco1/repos","events_url":"https://api.github.com/users/Fuco1/events{/privacy}","received_events_url":"https://api.github.com/users/Fuco1/received_events","type":"User","site_admin":false},"created_at":"2015-10-31T19:13:57Z","updated_at":"2015-10-31T19:13:57Z","body":"There was a bug indeed which triggered when there was an unmatched paren inside a string which directly touched a closing paren (pretty involved right? :D)\r\n\r\nIt should be fixed now.  I'll add your cases to the test suite so we don't run into it again.\r\n\r\nCan you test if it works for you now?"}}