Description

David Wilson (daviwil)

opened on May 24, 2016

Issue body actions

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

• [powershell] configuration and node keywords aren't highlighted microsoft/vscode#3342
• vscode-powershell issues with label syntax-bug

Sublime Text

• Issues with label area:Syntax

Atom

• Are there Powershell flag highlighting inconsistencies? jrsconfitto/language-powershell#24

Guillermo López-Anglada (@guillermooo) @jugglingnutcase sergei (@vors) Joel Bennett (@Jaykul) Øyvind Kallstad (@gravejester)

Activity

1. David Wilson (daviwil)

   added

   help wanted

   on May 24, 2016
2. hashhar commented on Aug 31, 2016

   

   Ashhar Hasan (hashhar)

   on Aug 31, 2016

   More actions

   I can try writing a script to import the issues. I will let you know within the week.
3. jrsconfitto commented on Aug 31, 2016

   

   James Sconfitto (jrsconfitto)

   on Aug 31, 2016

   More actions

   I just used this application to do it: https://github-issue-mover.appspot.com/

   Looks like it's run by Google (@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.

   Reacted by Ashhar Hasan and sergei
4. hashhar commented on Aug 31, 2016

   

   Ashhar Hasan (hashhar)

   on Aug 31, 2016

   More actions

   @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.
5. jrsconfitto commented on Aug 31, 2016

   

   James Sconfitto (jrsconfitto)

   on Aug 31, 2016

   More actions

   I'm fine with it closing the original issue on my repo, I guess other people may want a different behavior, though.
6. hashhar commented on Aug 31, 2016

   

   Ashhar Hasan (hashhar)

   on Aug 31, 2016

   More actions

   @jugglingnutcase I'll try and see if I can manage to fork the repo to behave that way.
7. hashhar commented on Sep 16, 2016

   

   Ashhar Hasan (hashhar)

   on Sep 16, 2016

   More actions

   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.
8. omniomi commented on May 21, 2018

   

   Nick James (omniomi)

   on May 21, 2018

   Contributor

   More actions

   Closing as the vast majority of issues were indeed moved or resubmitted.
9. Nick James (omniomi)

   closed this as completedon May 21, 2018

Issue actions