Ticket #196 (new defect)

Opened 19 months ago

Last modified 19 months ago

plugin paths into config file

Reported by: richardh Owned by:
Priority: major Milestone:
Component: plugins Version: 0.22
Keywords: Cc:

Description

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?

Change History

Changed 19 months ago by 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.

Note: See TracTickets for help on using tickets.