Ticket #196 (closed defect: not relevant)
Padre::Plugin::Parrot plugin paths into config file
|Reported by:||richardh||Owned by:||szabgab, azawawi, Alias|
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?
- Keywords Parrot Perl6 added
- Owner set to szabgab, azawawi, Alias
- Summary changed from plugin paths into config file to Padre::Plugin::Parrot plugin paths into config file
- Status changed from new to assigned
- Priority changed from major to trivial