plugin paths into config file

[richardh]

Error occurs with Padre::Plugin::Parrot

Installation of Plugin requires PARROT_PATH to be set to where parrot is resident, as currently parrot is not guarantted to be installed anywhere in particular.

But when Padre is started and the parrot plugin is used, PARROT_PATH is no longer available in the environment.

Since this is a configuration issue, should it not be in config file, with the relevant entry placed there by the plugin installation?

[szabgab]

I am not sure I understand the issue.
You have to have PARROT_PATH set in your .bashrc or whatever you might have so it will be available both during installation and when you launch padre.