This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 100124 - Script without extensions are not recognized in the OutputWindow
Summary: Script without extensions are not recognized in the OutputWindow
Status: RESOLVED FIXED
Alias: None
Product: ruby
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: All All
: P4 blocker (vote)
Assignee: Torbjorn Norbye
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-05 16:05 UTC by Martin Krauskopf
Modified: 2007-09-03 16:54 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Krauskopf 2007-04-05 16:05:50 UTC
Either the RubyExecution.RUBY_COMPILER may be black-magically enhanced or we
could start to use more than one OutputRecognizer. E.g.

public class RubyExecution extends ExecutionService {
  ...
  psfs RE_BASE = "^((\\[|\\]|\\-|\\:|[0-9]|\\s|\\,)*)(\\s*from )";
  psfs RegexpOutputRecognizer RUBY_COMPILER_NO_EXT =
    new RegexpOutputRecognizer(RE_BASE + "?(\\S.*)\\:([0-9]+):in.*", // [1]
      4, 5, -1);
  psfs RegexpOutputRecognizer RUBY_COMPILER =
    new RegexpOutputRecognizer(RE_BASE + "?(\\S.*\\.(rb|rake))\\:([0-9]+).*",
      4, 6, -1);
  ...
} // + // NOI18N

[1] 'in' to prevent a lot of non-sense matches.

Also the RUBY_COMPILER recognizer is used (almost?) everywhere (probably 10+
places). So a method like ExecutionDescriptor.useDefaultRecognizers(boolean)
could be considered. Default would be true - in that case RUBY_COMPILER and
eventually RUBY_COMPILER_NO_EXT and others would be added by default -> no need
to call addOutputRecognizer(RubyExecution.RUBY_COMPILER) on all ED instances.
Comment 1 Torbjorn Norbye 2007-06-20 05:11:20 UTC
Agreed
Comment 2 Jiri Kovalsky 2007-07-03 14:07:41 UTC
Reassigning this issue to newly created 'ruby' component.
Comment 3 Martin Krauskopf 2007-09-03 16:54:37 UTC
This was fixed this some time ago during large changes in the relevant code.