{"action":"created","issue":{"url":"https://api.github.com/repos/divinites/gissues/issues/50","repository_url":"https://api.github.com/repos/divinites/gissues","labels_url":"https://api.github.com/repos/divinites/gissues/issues/50/labels{/name}","comments_url":"https://api.github.com/repos/divinites/gissues/issues/50/comments","events_url":"https://api.github.com/repos/divinites/gissues/issues/50/events","html_url":"https://github.com/divinites/gissues/issues/50","id":181084267,"number":50,"title":"[Feature request] Markdown syntax, which user is preferable, for GitHub issue creating","user":{"login":"Kristinita","id":17247677,"avatar_url":"https://avatars.githubusercontent.com/u/17247677?v=3","gravatar_id":"","url":"https://api.github.com/users/Kristinita","html_url":"https://github.com/Kristinita","followers_url":"https://api.github.com/users/Kristinita/followers","following_url":"https://api.github.com/users/Kristinita/following{/other_user}","gists_url":"https://api.github.com/users/Kristinita/gists{/gist_id}","starred_url":"https://api.github.com/users/Kristinita/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Kristinita/subscriptions","organizations_url":"https://api.github.com/users/Kristinita/orgs","repos_url":"https://api.github.com/users/Kristinita/repos","events_url":"https://api.github.com/users/Kristinita/events{/privacy}","received_events_url":"https://api.github.com/users/Kristinita/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2016-10-05T07:38:45Z","updated_at":"2016-10-05T08:38:54Z","closed_at":null,"body":"### Request\n\nAdd by default the possibility to select for creating new issue syntax that the user typically uses for Markdown documents.\n\n### Justification\n\n1. In `MarkdownEditing — Markdown GFM` syntax I have many snippets, completions, macros and syntax highlight for computer languages when I use only in Markdown GFM syntax. When I do not use snippets, completions, macros and syntax highlight for computer languages I spend a lot of time.\n2. Since GitHub Issues use Markdown markup, I see no point in creating an additional syntax, if we have syntaxes for Markdown.\n\n### Extended behavior\n\n`GitHub Issue: Create Issue` → I select user/repository → GitHub Issue file always was opened in `MarkdownEditing — Markdown GFM` syntax (or other syntax, which users use for Markdown documents), not `GitHub Issue — Markdown` syntax. \n\n### Not helped\n\nI can not always use for issues crating MarkdownEditing — Markdown GFM syntax because file, when I wrote issue, not have extension. I can not add my preferable Markdown syntax for create issue file:\n\n1. `View` → `Syntax` → `Open all with current extension as...` → `MarkdownEditing` → `Markdown GFM`.\n2. [ApplySyntax](https://github.com/facelessuser/ApplySyntax) plugin.\n\n### Environment\n\n**Operating system and version:**\nWindows 10.0.14393\n**Sublime Text:**\nBuild 3126\n\n\nThanks.\n"},"comment":{"url":"https://api.github.com/repos/divinites/gissues/issues/comments/251615709","html_url":"https://github.com/divinites/gissues/issues/50#issuecomment-251615709","issue_url":"https://api.github.com/repos/divinites/gissues/issues/50","id":251615709,"user":{"login":"divinites","id":7761537,"avatar_url":"https://avatars.githubusercontent.com/u/7761537?v=3","gravatar_id":"","url":"https://api.github.com/users/divinites","html_url":"https://github.com/divinites","followers_url":"https://api.github.com/users/divinites/followers","following_url":"https://api.github.com/users/divinites/following{/other_user}","gists_url":"https://api.github.com/users/divinites/gists{/gist_id}","starred_url":"https://api.github.com/users/divinites/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/divinites/subscriptions","organizations_url":"https://api.github.com/users/divinites/orgs","repos_url":"https://api.github.com/users/divinites/repos","events_url":"https://api.github.com/users/divinites/events{/privacy}","received_events_url":"https://api.github.com/users/divinites/received_events","type":"User","site_admin":false},"created_at":"2016-10-05T08:38:54Z","updated_at":"2016-10-05T08:38:54Z","body":"@kristinita,  Thanks for the feature request. As far as I know, Sublime Text have a very convenient way to change current view's syntax.\n\nIn a Windows env, you can type <kbd>ctrl + shift + p </kbd> to open command palette, and type `sstx markdown`, and you will be able to see all Markdown related syntax.\n\nMaybe you have paid attention to the fact that I have changed the default issue syntax from MarkdownGFM to Sublime Text's Default Markdown, I did this for three reasons:\n\n- The default Markdown Syntax is error-free, no annoying errors like \n```\nError loading scope:source.css, source.less: Unable to find syntax file for scope source.css, source.less in Packages/GitHubIssue/issue.tmLanguage\nError loading scope:source.coffee: Unable to find syntax file for scope source.coffee in Packages/GitHubIssue/issue.tmLanguage\nError loading scope:source.scheme: Unable to find syntax file for scope source.scheme in Packages/GitHubIssue/issue.tmLanguage\nError loading scope:source.css, source.sass: Unable to find syntax file for scope source.css, source.sass in Packages/GitHubIssue/issue.tmLanguage\nError loading scope:source.swift: Unable to find syntax file for scope source.swift in Packages/GitHubIssue/issue.tmLanguage\nrule scope:source.scala#xml-comments has a scope name, but is unreachable, so the name will never be used\n```\n\n- The default markdown syntax adopted the new format `.sublime-syntax` instead of `.tmLanguage` which is actually TextMate syntax definition.\n\n- Since the plug-in use <kbd>ctrl+s</kbd> and <kbd>ctrl+shift+s</kbd> as the default short-cut of `github_update_issue` and `github_post_issue`, to avoid conflicting with the system default behaviour (<kbd>ctrl+s</kbd> for quick save, it is a very important shortcut system-wide!) I need to have a specific syntax definition and impose a constraint (scope selector) to make sure that these shortcuts are only valid in this specific syntax definition. \n\nTo sum up, there have to be a default syntax for issues and comments to avoid shortcut conflicts. But you do have the freedom to override the syntax using `command palette`. Once you switch to another syntax, the shortcuts will no more work and you will have to run all commands through `command palette` too."}}
{"actor":{"display_login":"divinites"}}