Skip to content

1.1.0

Compare
Choose a tag to compare
@saurabhdaware saurabhdaware released this 07 Sep 21:31
f06a93a
npm install -g projectman@1.1.0
  • Project specific editors (Thanks #4 @fechy for issue)
    • Now you can pm edit and set editor key in settings.json projects[] with the value of the command of your editor.
    • settings.json E.g.
{
    "commandToOpen": "code",
    "projects": [
        {
            "name":"MyCoolProject",
            "path":"/home/path/projects/mycoolproject",
            "editor":"vim"
        },
        {
            "name":"TwoProject",
            "path":"/path/something/project"
        }
    ]
}

This will allow users to open other projects in VSCode but use Vim to open MyCoolProject

  • Projects will not be erased after updating furthur
    (However they will still be erased while installing this update so I'll recommend to take copy of your settings.json If you have added multiple projects already) (Sorry but this is the last time when you'll have to do this 😢 ))
    (Thank you @codyaverett and @Tanuj69 issue #2 and helping me out solving this)
  • Added vim in pm seteditor
    also added a message explaining 'How to set editors/IDE that are not listed in the menu'
  • pm is now alias for pm open
    (Thank you @johannesjo for suggestion)
  • pm seteditor [commandToOpenEditor] added
    This will set default editor command, This can be used when the editor you want to use is not listed in pm seteditor. (Note: pm seteditor will work exactly same as it did before)