{"action":"created","issue":{"url":"https://api.github.com/repos/tpope/vim-markdown/issues/79","labels_url":"https://api.github.com/repos/tpope/vim-markdown/issues/79/labels{/name}","comments_url":"https://api.github.com/repos/tpope/vim-markdown/issues/79/comments","events_url":"https://api.github.com/repos/tpope/vim-markdown/issues/79/events","html_url":"https://github.com/tpope/vim-markdown/issues/79","id":97355830,"number":79,"title":"Make highlighting of markdownError optional","user":{"login":"blueyed","id":9766,"avatar_url":"https://avatars.githubusercontent.com/u/9766?v=3","gravatar_id":"","url":"https://api.github.com/users/blueyed","html_url":"https://github.com/blueyed","followers_url":"https://api.github.com/users/blueyed/followers","following_url":"https://api.github.com/users/blueyed/following{/other_user}","gists_url":"https://api.github.com/users/blueyed/gists{/gist_id}","starred_url":"https://api.github.com/users/blueyed/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/blueyed/subscriptions","organizations_url":"https://api.github.com/users/blueyed/orgs","repos_url":"https://api.github.com/users/blueyed/repos","events_url":"https://api.github.com/users/blueyed/events{/privacy}","received_events_url":"https://api.github.com/users/blueyed/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-07-26T22:40:08Z","updated_at":"2015-11-12T22:24:44Z","closed_at":null,"body":"I would like to disable highlighting of `markdownError`.\r\n\r\n> syn match markdownError \"\\w\\@<=_\\w\\@=\"\r\n\r\nDo you think an optional setting like `markdown_no_error` makes sense?\r\n(or `markdown_no_underscore_error` in case this should be more specific)\r\n\r\nMy case at hand is including Markdown syntax for Lua comments.  But also in other situations I've found that \"foo_bar\" would not trigger emphasizing after `_`.\r\n\r\nI've only skimmed http://spec.commonmark.org/0.21/#emphasis-and-strong-emphasis (and know that there are other implementations), but it appears that most would handle `foo_bar` as just \"foo_bar\" and not `foo<em>bar`.\r\n\r\nTherefore I think the default should maybe even be to not display this type of error - but others might be added in the future?!"},"comment":{"url":"https://api.github.com/repos/tpope/vim-markdown/issues/comments/156256443","html_url":"https://github.com/tpope/vim-markdown/issues/79#issuecomment-156256443","issue_url":"https://api.github.com/repos/tpope/vim-markdown/issues/79","id":156256443,"user":{"login":"blueyed","id":9766,"avatar_url":"https://avatars.githubusercontent.com/u/9766?v=3","gravatar_id":"","url":"https://api.github.com/users/blueyed","html_url":"https://github.com/blueyed","followers_url":"https://api.github.com/users/blueyed/followers","following_url":"https://api.github.com/users/blueyed/following{/other_user}","gists_url":"https://api.github.com/users/blueyed/gists{/gist_id}","starred_url":"https://api.github.com/users/blueyed/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/blueyed/subscriptions","organizations_url":"https://api.github.com/users/blueyed/orgs","repos_url":"https://api.github.com/users/blueyed/repos","events_url":"https://api.github.com/users/blueyed/events{/privacy}","received_events_url":"https://api.github.com/users/blueyed/received_events","type":"User","site_admin":false},"created_at":"2015-11-12T22:24:44Z","updated_at":"2015-11-12T22:24:44Z","body":"@ptzz \r\nThanks.\r\n\r\nI've found that this would then start highlighting the `_bar` in `foo_bar` as italic instead.\r\n\r\nI am now using this:\r\n\r\n    autocmd FileType markdown hi link markdownError NONE"}}