-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
First step: move all known issues for the existing TextMate grammar to this repo #1
Comments
I can try writing a script to import the issues. I will let you know within the week. |
I just used this application to do it: https://github-issue-mover.appspot.com/ Looks like it's run by @google: see the code in their org: https://github.com/google/github-issue-mover It was pretty easy to migrate the issues with: someone with access to the original repo with issues need to auth the app and then paste a couple links with the old issue and this repository. Edit: it doesn't move a ton of issues easily that I can see, though. Maybe a script would work better for the SublimeText owners. |
@jugglingnutcase I think this will serve well for repos hosted on GitHub. And it seems like quite a lot of people use it. The only problem is that it closes the original issues. We can maybe fork it to fix that. |
I'm fine with it closing the original issue on my repo, I guess other people may want a different behavior, though. |
@jugglingnutcase I'll try and see if I can manage to fork the repo to behave that way. |
I'm sorry but I couldn't get the tool to work that way. I'll have to write a script. Sorry for the delay. |
Closing as the vast majority of issues were indeed moved or resubmitted. |
Since we're now centralizing development of the TextMate definition for PowerShell in this repo, it'd be good to find all known issues with the current state of the syntax definition and move them to this repo. It'd be great to have some help doing this (especially if someone can find a way to automate it 😉)
Here are some starting points:
Visual Studio Code
configuration
andnode
keywords aren't highlighted microsoft/vscode#3342syntax-bug
Sublime Text
Atom
@guillermooo @jugglingnutcase @vors @Jaykul @gravejester
The text was updated successfully, but these errors were encountered: