#528 Content-type does not enable to run/debug perl scripts

v0.6.x
closed-fixed
nobody
Core (65)
5
2009-02-07
2008-12-16
Anonymous
No

I often create perl files without file extensions: they are to be used as commands from the CLI.

With EPIC, such files are not detected as perl files. I tried to force perl association by creating a content type for each of these files: It seems to work, since they now appear in the project with the little camel (plus properties says it is a "File (Perl Source File)").

The problem is that the "Run as" and "Debug as" functions continue to say "(none applicable)".

I would like to see here "Perl Local".

Olivier

Discussion

  • Jan Ploski

    Jan Ploski - 2009-02-07

    Fixed in 0.6.30.

     
  • Jan Ploski

    Jan Ploski - 2009-02-07
    • status: open --> closed-fixed
     

Log in to post a comment.