Closed Kristinita closed 8 years ago
@Kristinita Since you are using Markdown GFM syntax instead of the built-in issue.sublime-syntax, could you please tell me if auto-completion feature works for you? the newest version just added commit auto-completion: a251d62bab211d6a26adfa5489ca03aeb903ca97 so now almost everything is auto-completable such as label, other issues, discussants and commits.
@divinites , please, may you add in README.MD
screencasts of extended behavior auto-completion? Now I do not know how should work your autocompletes. Thanks.
@Kristinita I have added two screenshots. One for label auto-completion, the other for issue title, commits and participants auto-completion.
@divinites , none autocomplete not work for me 😿. Thanks.
Yes, it is understandable. @Kristinita if you open github_issue.sublime-settings
, you will find it has been updated.
{
"token": "",
"username": "",
"password": "",
"debug": 0,
"syntax": "Packages/GitHubIssue/Issue.sublime-syntax",
"git_path": "",
"issue_title_completion": true,
"user_completion": true,
"label_completion": true,
"commit_completion": true,
"commit_completion_trigger": ":",
"custom_completion_scope": []
}
fill in the "custom_completion_scope" with your markdown scope, if you are using Markdown GFM, then In your user setting file, it should be:
"custom_completion_scope": ["text.html.markdown.gfm"]
If it does not work, please let me know the console output.
Also,
none autocomplete not work for me
is double negative, which actually means that all autocompletes work for you. I believe that it is not the meaning that you want to express.
is double negative, which actually means that all autocompletes work for you. I believe that it is not the meaning that you want to express.
I'm sorry, I know English bad. You also incorrectly wrote a message in Russian language 😸.
@divinites, now all autocompletes works for me, but I need press Ctrl+Space, to get autocomplete variants.
I find in my User/Preferences.sublime-settings
file these lines
"auto_complete_triggers":
[
{
"characters": "<",
"selector": "text.html"
},
{
"characters": "@",
"selector": "text.html.github.issue"
},
{
"characters": "#",
"selector": "text.html.github.issue"
},
{
"characters": ":",
"selector": "text.html.github.issue"
},
{
"characters": "@",
"selector": "text.html.github.issue"
},
{
"characters": "#",
"selector": "text.html.github.issue"
},
{
"characters": ":",
"selector": "text.html.github.issue"
},
{
"characters": "@",
"selector": "text.html.github.issue"
},
{
"characters": "#",
"selector": "text.html.github.issue"
},
{
"characters": ":",
"selector": "text.html.github.issue"
}
],
Selector not automatically change for me.
I think that the symbol :
a bad solution to commit trigger by default, because symbol :
use on GitHub for smiles. I use GitHub Emoji plugin, after :
I get smiles in autocomplete.
Thanks.
commit & 45877c4eb3fdf36512e9f7ce8e47fc5533f20b5f should solve this problem. The selector will be your custom_scope and it will not make duplicated entries in perference.sublime-settings. Please delete
{
"characters": "@",
"selector": "text.html.github.issue"
},
{
"characters": "#",
"selector": "text.html.github.issue"
},
{
"characters": ":",
"selector": "text.html.github.issue"
},
{
"characters": "@",
"selector": "text.html.github.issue"
},
{
"characters": "#",
"selector": "text.html.github.issue"
},
{
"characters": ":",
"selector": "text.html.github.issue"
},
{
"characters": "@",
"selector": "text.html.github.issue"
},
{
"characters": "#",
"selector": "text.html.github.issue"
},
{
"characters": ":",
"selector": "text.html.github.issue"
}
In the file.
I will push a new release soon.
pushed v.2.3.2. @Kristinita
pushed v.2.3.5. Now the auto-completion feature is constrained inside the view, so it will not save in the disk and jeopardizes preferences.sublime-settings. @Kristinita now you can delete all trigger settings that this plug-in adds. I believe the initial settings is just:
"auto_complete_triggers":
[
{
"characters": "<",
"selector": "text.html"
}
],
None!