{"issue":{"pull_request":{"diff_url":null,"html_url":null,"patch_url":null},"state":"closed","user":{"avatar_url":"https://secure.gravatar.com/avatar/04f3babefa4ba85e7904b40e6846e217?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"04f3babefa4ba85e7904b40e6846e217","url":"https://api.github.com/users/purcell","login":"purcell","id":5636},"milestone":null,"labels":[],"assignee":null,"updated_at":"2011-11-10T12:52:10Z","closed_at":"2011-11-10T12:52:10Z","comments":1,"url":"https://api.github.com/repos/technomancy/clojure-mode/issues/34","body":"With Emacs HEAD and the latest clojure-mode from git, `check-parens` breaks when the following comment is in a file, claiming that there are unmatched parens.\r\n\r\n    ; e.g. Foo StartTime=\"2008-09-28T14:38:53Z\r\n\r\nI presume that the syntax table is slightly confused, and the unmatched quote therefore gets treated as a broken sexp; the same comment passes `check-parens` when dropped into an elisp file.\r\n\r\nWhen `check-parens` fails, `paredit` can't be enabled. (gasp!)\r\n\r\nI don't know if it's related, but I also noticed that emacs' notion of sexps varies between emacs-lisp and clojure source; in the former, any number of consecutive comments are treated as a single sexp for the purpose of `'forward-sexp` etc., even when separated by blank lines. In clojure-mode, forward-sexp at the beginning of this line:\r\n\r\n    ;; Parse dates/times in common string formats\r\n\r\nmoves point to just before \"Parse\". This seems like an error to me.\r\n\r\n-Steve","html_url":"https://github.com/technomancy/clojure-mode/issues/34","title":"Certain comments break check-parens (and hence paredit)","number":34,"id":1235088,"created_at":"2011-07-16T13:46:55Z"},"action":"closed"}