1.2.0-alpha.2

• --for-project flag added to pm seteditor
  Usage : pm seteditor [editorCommand] --for-project [projectName].

  • This will let users set editor for a specific project without pm edit
  • [editorCommand] and [projectName] are optional commands and will be asked as questions when the value is not given

1.2.0-alpha.1

npm install -g https://github.com/saurabhdaware/projectman#v1.2.0-alpha.1

• pm getpath [projectName] command added which will show you the path of project.
  This can be used as cd $(pm getpath) to cd to the project.

1.1.0

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)

---

1.1.0-rc.2

npm install -g https://github.com/saurabhdaware/projectman#v1.1.0-rc.2

CHANGELOG

• Project specific editors:

  • 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

---

• pm seteditor [commandToOpenEditor] added which 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)

---

1.1.0-rc.1

If you want to test BETA version of upcoming projectman you can try it out by installing with following command.

npm install -g https://github.com/saurabhdaware/projectman#v1.1.0-rc.1

• pm is now equivalent to pm open
• settings.json will not be erased after updating furthur (However it will still be erased while installing this update)
• Added vim in pm seteditor and added a message explaining 'How to set editors/IDE that are not listed in the menu'

1.0.0

npm install -g projectman@1.0.0

Initial release of ProjectMan.

Includes following commands:

pm add
pm remove
pm open
pm seteditor