{"action":"created","issue":{"url":"https://api.github.com/repos/tpope/vim-markdown/issues/94","labels_url":"https://api.github.com/repos/tpope/vim-markdown/issues/94/labels{/name}","comments_url":"https://api.github.com/repos/tpope/vim-markdown/issues/94/comments","events_url":"https://api.github.com/repos/tpope/vim-markdown/issues/94/events","html_url":"https://github.com/tpope/vim-markdown/issues/94","id":128411563,"number":94,"title":"Unnecessary limit to list indent depth","user":{"login":"rdeforest","id":3655371,"avatar_url":"https://avatars.githubusercontent.com/u/3655371?v=3","gravatar_id":"","url":"https://api.github.com/users/rdeforest","html_url":"https://github.com/rdeforest","followers_url":"https://api.github.com/users/rdeforest/followers","following_url":"https://api.github.com/users/rdeforest/following{/other_user}","gists_url":"https://api.github.com/users/rdeforest/gists{/gist_id}","starred_url":"https://api.github.com/users/rdeforest/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rdeforest/subscriptions","organizations_url":"https://api.github.com/users/rdeforest/orgs","repos_url":"https://api.github.com/users/rdeforest/repos","events_url":"https://api.github.com/users/rdeforest/events{/privacy}","received_events_url":"https://api.github.com/users/rdeforest/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2016-01-24T17:19:11Z","updated_at":"2016-01-24T17:55:29Z","closed_at":null,"body":"On lines 64 and 65 of syntax.vim (as of commit 63074a5), the number of spaces is 0 to 4:\r\n\r\n    syn match markdownListMarker \"\\%(\\t\\| \\{0,4\\}\\)[-*+]\\%(\\s\\+\\S\\)\\@=\" contained\r\n\r\nIs there a reason to include a maximum number of spaces instead of using \"\\{0,\\}\" or the more common '*' to indicate zero or more spaces? Is this related to the four-space indent for monospace text blocks? (I've switched to plasticboy's plugin in the short term rather than digging into this myself.)\r\n\r\nUnrelated to that, but not worthy of its own issue, line four of the comment header is not strictly accurate:\r\n\r\n    \" Last Change:  2013 May 30\r\n\r\nEither automatically update it with some git scripting magic or remove the line entirely."},"comment":{"url":"https://api.github.com/repos/tpope/vim-markdown/issues/comments/174323851","html_url":"https://github.com/tpope/vim-markdown/issues/94#issuecomment-174323851","issue_url":"https://api.github.com/repos/tpope/vim-markdown/issues/94","id":174323851,"user":{"login":"rdeforest","id":3655371,"avatar_url":"https://avatars.githubusercontent.com/u/3655371?v=3","gravatar_id":"","url":"https://api.github.com/users/rdeforest","html_url":"https://github.com/rdeforest","followers_url":"https://api.github.com/users/rdeforest/followers","following_url":"https://api.github.com/users/rdeforest/following{/other_user}","gists_url":"https://api.github.com/users/rdeforest/gists{/gist_id}","starred_url":"https://api.github.com/users/rdeforest/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rdeforest/subscriptions","organizations_url":"https://api.github.com/users/rdeforest/orgs","repos_url":"https://api.github.com/users/rdeforest/repos","events_url":"https://api.github.com/users/rdeforest/events{/privacy}","received_events_url":"https://api.github.com/users/rdeforest/received_events","type":"User","site_admin":false},"created_at":"2016-01-24T17:55:29Z","updated_at":"2016-01-24T17:55:29Z","body":"I meant also to mention in case it wasn't adequately implied: my real use case is actually much longer."}}