Ticket #196 (closed defect: not relevant)

Opened 5 years ago

Last modified 2 years ago

Padre::Plugin::Parrot plugin paths into config file

Reported by: richardh Owned by: szabgab, azawawi, Alias
Priority: trivial Milestone:
Component: plugins Version: 0.22
Keywords: Parrot Perl6 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

comment:1 Changed 5 years 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.

comment:2 Changed 3 years ago by bowtie

  • 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

As far as I can assertion, this should either be:

1, Marked "Not Reverent", as it's a user's local configuration issue.

or

2, Do we need a mod to Padre::PluginManager to check for valid env{ } used by a plugin.

my 2d is for Not Relevant :)

comment:3 Changed 2 years ago by azawawi

  • Status changed from assigned to closed
  • Resolution set to not relevant
Note: See TracTickets for help on using tickets.