kimerdle / perl-on-netbeans

Automatically exported from code.google.com/p/perl-on-netbeans
0 stars 0 forks source link

Useless setting for the Perl executable #34

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
There is a pre-requisite mentioned in the plug-in introduction: The Perl and 
Java binaries should be available in the PATH variable of your system.

In the NetBeans menu: Tools -> Options -> Perl On NetBeans -> General also has
a textbox where a path of the Perl executable can be provided.

The latter option has no effect.

My suggestion: remove the requirement for the location of the Perl executable 
in the PATH variable. Use the path of the Perl executable specified in Perl On 
Netbeans settings under Tools -> Options.

I am using NetBeans 8.0.2 on Windows 8.1 and Perl 5.20.1 built for 
x86_64-msys-thread-multi (MSYS2 or msys64).

I do not include too many locations in the PATH variable to avoid possible 
conflicts between binaries with the same name but different interfaces. 
Therefore, I would prefer to make settings when they are actually needed. My 
current workaround for this issue: in the commandline window, add the Perl 
binary location to the Path variable and then launch NetBeans from that 
commandline window.

Original issue reported on code.google.com by jslap...@gmail.com on 1 Jan 2015 at 10:03

GoogleCodeExporter commented 9 years ago
PATH is required in case you are a beginner. For experienced users, the option 
to add the Perl binary in the Tools -> Options menu would over-ride the entry 
in PATH. Even if you have both, the entry in Tools -> Options takes priority. 

Tested with Perl On NetBeans 0.3 on NetBeans 8 and Windows 7. Please refer to 
the testing evidence attached here and feel free to respond in case you need 
further clarifications.

Original comment by sudeepha...@gmail.com on 6 Jan 2015 at 12:04

Attachments:

GoogleCodeExporter commented 9 years ago
Closing issue as positive tests are observed.

Original comment by sudeepha...@gmail.com on 6 Jan 2015 at 12:05

GoogleCodeExporter commented 9 years ago
I also tested it on Windows 7 and everything was fine.
But I reported about the issue on Windows 8.1 (64-bit version at least).

Original comment by jslap...@gmail.com on 11 Jan 2015 at 2:42

GoogleCodeExporter commented 9 years ago
The current version is tested on Windows 7. I am reopening the defect and will 
investigate further.

Original comment by sudeepha...@gmail.com on 14 Jan 2015 at 12:57