Hi, I have not experienced your issue, with various versions of Perl and EPIC, all on Windows 10. I have not tried to run your program, but here are a few items you could try. The first line sets a variable you can use to conditionally execute code while running under EPIC. my $running_with_debugger = 1 if ($ENV{PERLDB_PIDS} eq $$); # $$ is the process ID of the current perl script STDOUT->autoflush(1); # To make sure messages are not printed out of order STDERR->autoflush(1); # To make sure messages...
Well, so $\ = "\n" it is. (Why) do you need it? The short answer is because I do. I might point out that, in the meantime, I've been using Devel::ptkdb which doesn't have this limitation. It seems strange to have to write code around the debugger's tastes. It should at least be documented so the writing-around can be accomplished. Are there any other debugger preferences that I should be aware of? I'd also suggest you use the JSON::XS module for JSON parsing Everybody's a critic :) I'm sure JSON::XS...
It's the part $\ = "\n"; which messes it up. (Why) do you need it? (I'd also suggest you use the JSON::XS module for JSON parsing.)
FWIW: I have PadWalker 2.3 installed.
Umm, that didn't get formatted well. Not sure how to get the vertical bars to display,
The debugger consol is displaying the value. use strict; use JSON::Parse ':all'; $\ = "\n"; $,= ' '; my $jsonFile = "/tmp/odds.json"; my $prl = json_file_to_perl ($jsonFile); Debug Console output: 15: my $prl = json_file_to_perl ($jsonFile); DB<10> ;{ do 'dumpvar_epic.pm' unless defined &dumpvar_epic::dump_lexical_vars; my $offset = 0; my $savout = CORE::select($DB::OUT); dumpvar_epic::dump_lexical_vars($offset); CORE::select($savout); }; 9 $jsonFile 1 1 17 SCALAR(0x2437ec8) 16 '/tmp/odds.json' 2...
I just tried with a similar configuation (freshly compiled Perl 5.28.1, PadWalker 2.3, Eclipse 2019-06), and it works for me. Is the error displayed for any code or something very specific (the error may have to do with unusual content of variables to be dumped)? Any clues if you "Enable debugger console (experimental)" in Preferences > Perl? (The additional console will become available from the Debug view when you relaunch the debug configuration.)
Can't view variables when debugging
EPIC (for Perl integration with Eclipse) plugin incompatible with Eclipse IDE 2019-12
The Navigator View is scheduled for removal by Eclipse after August 2021.
Let the user optionally use another version of Perl::Tidy
It looks like qw ( LIST ) works properly always, but qw / LIST / works properly only if the LIST contains odd number of entities. Furhtermore, qw /:standard/ doesn't work, althought the LIST contains just odd number of entities, however qw / strftime/ works fine, as well as qw /+conns/, so in this particular case the : character seems to be the one that cause the problem.
Some observations: works properly: use Encode qw / encode_utf8/; works properly: use Encode qw ( encode_utf8); doesn't work properly: use CGI qw /:standard/; works properly: use CGI qw (:standard); doesn't work properly: use HTTP::Request qw / /; works properly: use HTTP::Request qw ( ); doesn't work properly: use HTTP::Request::Common qw / GET POST/; works properly: use HTTP::Request::Common qw ( GET POST);
Formatting of `qw` is not working as expected
If the code is written as $data{'flag'} = ($@) ? flag_post : (flag_post | flag_data); then there is no problem with formatting, so I assume the problem is in recognision of $@ variable.
If the code is formatted as $data{'flag'} = ($@) ? flag_post : (flag_post | flag_data); then there is no problem with formatting, so I assume the problem is in recognision of $@ variable.
Incorrect syntax formatting
qq#string# is not supported
this is the EOF end screenshot
wrong sytax highting when here documents is too long
Hello, I am quite new to Perl. I work under Eclipse with EPIC, Strawberry Perl & PadWalker under Windows10. When I run Debug with breakpoints, The programm stops well if the breakpoints are in the main function, but does not if breakpoints are in functions belonging to other modules. Any idea how to solve that problem? Thank you for your help Alex
STDERR is not showing in console during debugging
I'm somewhat sure to have installed EPIC from the marketplace some months ago and there's a page available: https://marketplace.eclipse.org/content/epic-eclipse-perl-integration#group-details But now, the marketplace client within Eclipse can't find it anymore. Any idea about the problem?
I'm somewhat sure to have installed EPIC from the marketplace some months ago, but now I can't find it there anymore. Has it ever been published there? If so, any idea what could be the problem now?
Sorry, ignore the second regex, it works fine. The problem is only the first "/".
Syntax highlighting broken after some special chars
I've notices this coloring issue. It makes the all file unreadable and brakes outline view. I'm using EPIC for more than 6 years now. I love Eclipse so thanks a lot for EPIC editor.
Ouch, I now see that you mentioned Perl 5.6 - this is 18 years old by now... Yes, you should use a more recent Perl version.
Ok, I got it! Can't locate Encode.pm in @INC (@INC contains: C:/Perl/lib C:/Perl/site/lib .) at Perl/Tidy.pm line79. It seems that my Perl installation is missing the Encode module. I've tried another Perl version (just an old test installation 5.14.x) in which the module exists and et voila it works! Now I need to convince my IT admins to release a newer version with the module, but this is not your problem. Please close this ticket. Many Thanks for your help Andreas
Ok, I got it! Can't locate Encode.pm in @INC (@INC contains: C:/Perl/lib C:/Perl/site/lib .) at Perl/Tidy.pm line79. It seems that my Perl installation is missing the Encode module. I've tried another Perl version (just an old test installation 5.14.x) in which the module exists and et voila it works! Now I need to convince my IT admins to release a newer version with the module, but this is not your problem. Many Thanks for your help Andreas
You are probably in wrong directory. You're supposed to "cd \Projects\Perl.metadata.plugins\org.epic.perleditor\perlutils" first and then run the "C:\Perl\bin\Perl.exe" perltidy params < sourcefile.pl from there.
Hmm, ... It looks like perltidy can not find the Tidy.pm module in the Perl subfolder. "C:\Perl\bin\Perl.exe" "C:\Projects\Perl\.metadata\.plugins\org.epic.perleditor\perlutils\perltidy\perltidy" "-q" "--indent-columns=4" "--maximum-line-length=200" "--opening-brace-on-new-line" "--line-up-parentheses" "C:\Projects\Perl\PTests\ptest_FnkCall.pl" Can't locate Perl/Tidy.pm in @INC (@INC contains: C:/Perl/lib C:/Perl/site/lib .) at C:\Projects\Perl\.metadata\.plugins\org.epic.perleditor\perlutils\perltidy\perltidy...
I also tried to get around this by setting the .perltidyrc into my project root folder but this neither helped.
Try running that comand line yourself from the cmd.exe prompt, after changing to the working directory mentioned in my first reply and piping the source file to be formatted as standard input. It may be that perltidy is aborting for some reason, perhaps because of the content of your source file. Does it work with other ("Hello world") files?
Thank you for your quick answer. Try specifying an aboslute path to Perl executable in Window > Preferences > Perl. Check workspace/.metadata/.log if it contains more details about why the exectuion failed. Sadly after setting an absolute path the error stays the same. Here is excerpt for my log file: !ENTRY org.epic.perleditor 4 0 2018-11-14 15:03:00.126 !MESSAGE Failed to execute command line: "C:\Perl\bin\Perl.exe" "perltidy" "-q" "--indent-columns=4" "--maximum-line-length=200" "--opening-brace-on-new-line"...
Try specifying an aboslute path to Perl executable in Window > Preferences > Perl. Check workspace/.metadata/.log if it contains more details about why the exectuion failed. What's supposed to happen when you invoke the Source > Format function is that the command line you quoted as failed is executed in working directory workspace/.metadata/.plugins/org.epic.perleditor/perlutils/perltidy - into which the perltidy version shipped with EPIC is extracted beforehand.
Formatter error since EPIC 0.7
EPIC 0.7.7 seems to work for me. Environment: Windows 10 ActivePerl 5.26.1 Java 1.8 Eclipse Photon (4.8) EPIC 0.7.7
Ok, I changed the code in 0.7.7 to rely on :raw and on the Encode module. I also discovered and hopefully fixed more bugs with transfer of non-ASCII values or variable names from perldb into the "Variables" view and another one with signalling truncation of large (>64K) values...
I added this fix - binmode($DB::OUT, ':encoding(UTF-8)') rather than binmode($DB::OUT, ':utf-8') to EPIC 0.7.6 now. Please have a look at the original bug ticket and patches again, in my opinion it makes very clear that using ":encoding(...)" is deprecated as well: +(W deprecated) The sysread(), recv(), syswrite() and send() operators +are deprecated on handles that have the C<:utf8> layer, either +explicitly, or implicitly, eg., with the C<:encoding(UTF-16LE)> layer. https://rt.perl.org/Public/Ticket/Attachment/1360169/728149/0001-perl-125760-deprecate-sys-read-write-send-recv-on-ut.patch...
I added this fix - binmode($DB::OUT, ':encoding(UTF-8)') rather than binmode($DB::OUT, ':utf-8') to EPIC 0.7.6 now. Please have a look at the original bug ticket and patches again, in my opinion it makes very clear that using ":encoding(...)" is deprecated as well: +(W deprecated) The sysread(), recv(), syswrite() and send() operators +are deprecated on handles that have the C<:utf8> layer, either +explicitly, or implicitly, eg., with the C<:encoding(UTF-16LE)> layer. https://rt.perl.org/Public/Ticket/Attachment/1360169/728149/0001-perl-125760-deprecate-sys-read-write-send-recv-on-ut.patch...
I added this fix - binmode($DB::OUT, ':encoding(UTF-8)') rather than binmode($DB::OUT, ':utf-8') to EPIC 0.7.6 now. Please have a look at the original bug ticket and patches again, it makes very clear that using ":encoding(...)" is deprecated as well: +(W deprecated) The sysread(), recv(), syswrite() and send() operators +are deprecated on handles that have the C<:utf8> layer, either +explicitly, or implicitly, eg., with the C<:encoding(UTF-16LE)> layer. https://rt.perl.org/Public/Ticket/Attachment/1360169/728149/0001-perl-125760-deprecate-sys-read-write-send-recv-on-ut.patch...
Jan, EPIC 0.7.6 seems to work for me. Thanks! Environment: Windows 10 ActivePerl 5.26.1 Java 1.8 Eclipse Photon (4.8) EPIC 0.7.6 No customized version of dumpvar_epic.pm
I added this fix - binmode($DB::OUT, ':encoding(UTF-8)') rather than binmode($DB::OUT, ':utf-8') to EPIC 0.7.6 now. The automated tests seem to be still working. Can you test if this new version installs and works ok for you? Note that EPIC 0.7.6 now requires at least Java SE 7 to execute (so don't upgrade if you must stay with Java SE 6.0).
Dave, Thanks for the fix. I also had problems with EPIC 0.7.5, which were fixed by: 1. editing line 123 of the 0.7.5 version dumpvarepic.pm as "binmode($DB::OUT, ':encoding(UTF-8)');" 2. putting this copy of dumpvarepic.pm in a directory outside the Eclipse workspace 3. adding this directory to the list of directories in the "Perl Include Path" properties of the relevant Eclipse project Just to be clear, upgrading to EPIC 0.7.5 alone didn't fix my problem. This is on Eclipse Photon (4.8).
EPIC seems to not suggest methods named completely in upper case or starting with _ in Content Assist. Is there some way to at least change the behaviour for upper case? I use that naming convention for public constants and don't have the feeling that it's that uncommon in Perl or other languages. Not having Content Assist available for those constants is a bit annoying. Thanks!
I'm glad it has helped you :) Steve On Tue, 11 Sep 2018 at 12:54, Liang Xu mosxl@users.sourceforge.net wrote: Thank you Jan and Steve, I also got the issue fixed with your solution. Hope this issue would be fixed permanently in the future. [bugs:#700] https://sourceforge.net/p/e-p-i-c/bugs/700/ Ticket #698 not solved in EPIC 0.7.5* Status: open Group: v0.7.x Created: Thu May 17, 2018 08:19 PM UTC by Mike Last Updated: Wed Aug 29, 2018 09:05 PM UTC Owner: nobody the issue still occurs. Is it possible...
Thank you Jan and Steve, I also got the issue fixed with your solution. Hope this issue would be fixed permanently in the future.
I'm very pleased to know it has helped you :) Steve On Thu, 30 Aug 2018 at 07:05, Dave Wilbur dvwilbur@users.sourceforge.net wrote: Thank you guys for this thread. I just got an upgraded machine at work and started to get this error after installing the latest Eclipse/EPIC. I have found that either binmode($DB::OUT, ':raw'); or binmode($DB::OUT, ':encoding(UTF-8)'); on line 123 of the new dumpvarepic.pm http://dumpvarepic.pm avoid the fatal warning while using the variables debug window to watch...
Thank you guys for this thread. I just got an upgraded machine at work and started to get this error after installing the latest Eclipse/EPIC. I have found that either binmode($DB::OUT, ':raw'); or binmode($DB::OUT, ':encoding(UTF-8)'); on line 123 of the new dumpvarepic.pm avoid the fatal warning while using the variables debug window to watch my variables. I'm not sure if the raw layer does anything different than standard binmode without specifying a layer. Based on what I've read in the various...
As for your fix, I'll test it, but I suspect that changing from :utf8 to :raw might have unwanted side effects of not being able to see UTF-8 characters[...] +1, changing to ":raw" alone doesn't make much sense if one explicitly worked with UTF-8 characters before. Using ":raw" in combination with explicitly encoding/decoding to/from UTF-8 before writing/after reading OTOH should be the proper solution. I often prefer "Encode::Ecode|decode" instead of "utf8::encode|decode", because it croaks on invalid...
As for your fix, I'll test it, but I suspect that changing from :utf8 to :raw might have unwanted side effects of not being able to see UTF-8 characters[...] +1, changing to ":raw" alone doesn't make much sense if one explicitly worked with UTF-8 characters before. Using ":raw" in combination with explicitly encoding/decoding to/from UTF-8 before writing/after reading OTOH should be the proper solution. I often prefer "Encode::Ecode|decode" instead of "utf8::encode|decode", because it croaks on invalid...
As for your fix, I'll test it, but I suspect that changing from :utf8 to :raw might have unwanted side effects of not being able to see UTF-8 characters[...] +1, changing to ":raw" alone doesn't make much sense if one explicitly requested UTF-8 characters before. Changing either to "read" while keeping the ":utf8"-layer or changing to ":raw" followed by "Encode::decode('UTF-8', $buffer, Encode::FB_CROAK()[ | Encode::LEAVE_SRC()])" on all read bytes seems to be the proper solution. "utf8::decode"...
Please move "Add/Remove Perl Nature" in "Configure" submenu.
Yes, the extraction always happens on every launch. But by prepending another directory to @INC path you are tricking the Perl interpreter into not using what EPIC would normally want it to use. As for your fix, I'll test it, but I suspect that changing from :utf8 to :raw might have unwanted side effects of not being able to see UTF-8 characters contained in variable values (maybe also in variable names in source code). If you want to test yourself, try "use utf8;" and add some variables with such...
Again, thank you Jan. I have the (experimental) debugger console enabled....now I know which checkbox turned it on! Thanks. I figured perl.exe was executing .pl/.pm...I didn't realise that 'dumpvar_epic.pm' was 'compiled' into the org.epic.debug_x.y.z.jar. I have dumpvar_epic.pm open in Notepad++ and I noticed just now as I was debugging my script that it reloaded after being changed on disk, but it is not my copy that changed....it is the normal copy under the ./org.epic.debug/...folder. So, it...
I think I fixed it, but I need someone who understands to verify it.... The second thread above (perl.org) documents the discussion and implementation of the exception we are seeing in the EPIC debugger (below). BTW, looking more closely at the exception message: --- BEGIN --- recv() is deprecated on :utf8 handles. This will be a fatal error in Perl 5.30 a t C:/Perl64/lib/IO/Socket.pm line 304. at C:/Perl64/lib/IO/Socket.pm line 304. IO::Socket::recv(IO::Socket::INET=GLOB(0x323f250), "", 2048) called...
dumpvar_epic.pm is picked via @INC (Perl include path) by the command "do" in dump_local_vars.pl and dump_global_vars.pl scripts (see https://github.com/jploski/epic-ide/tree/testing/org.epic.debug). The code of those two scripts, extracted from the plugins/org.epic.debug_x.y.z.jar archive found in your Eclipse install directory, is passed inline (with some context-related substitutions) through the STDIN stream to the Perl debugger process. So the answer is, perl.exe, which is running perl5db.pl,...
I just found these two link - I consider these authoritative. Could this lead us to the answer? From the Perly Gates: http://www.perlmonks.org/?node_id=1195588 And Mr Ed ('The Horse'): https://rt.perl.org/Public/Bug/Display.html?id=125760 (...forgive me if those references are too obtuse :) )
Hi Jan, First, thank you for the work you have done. I appreciate it. I have this problem too. I tried your suggestion above - created a copy of the two files in another folder which I added to the EPIC path list. It doesn't seem to use my copies. I amnot sure which process/exe actually calls the dumpvar_epic.pm module - perl.exe or the org.eclipse..jar file? I looked at the change you made to the source, read up what I could about the "binmode" command, "Perl::IO" encode, and the utf8 issue. Before...
I checked that the change has been rolled out in 0.7.5. What you can do is look in $WORKSPACE/.metadata/.plugins/org.epic.debug/ which is where EPIC writes its helper modules upon every launch (including perl5db.pl, which is a patched version of the Perl debugger, and dumpvar_epic.pm, which is where the particular fix for 0.7.5 got applied - https://github.com/jploski/epic-ide/commit/17579c6e289a6f7d57815efbd1f84c9a016cf16d). You can copy these helper modules from there to another directory (to avoid...
An IOException occurred while executing debugger command could not match re.IP_POS in {recv() is deprecated on :utf8 handles. This will be a fatal error in Perl 5.30 at D:/strawberry64/perl/lib/IO/Socket.pm line 304. at D:/strawberry64/perl/lib/IO/Socket.pm line 304. IO::Socket::recv(IO::Socket::INET=GLOB(0x5361980), "", 2048) called at D:/Eclipse/ws-pos/.metadata/.plugins/org.epic.debug/perl5db.pl line 7358 DB::readline(" DB<23> ") called at D:/Eclipse/ws-pos/.metadata/.plugins/org.epic.debug/perl5db.pl...
Ticket #698 not solved in EPIC 0.7.5
I'm using EPIC 0.7.5 and Perl 5.26 but still having the same problem when stepping through code - any ideas?
Bump? Switching to the testing version (0.7.5) resolved the error I was receiving trying to create a new Perl project: "http://www.epic-ide.org/updates/testing" A found a discussion that discussed this in BUG #691 "Cannot create Perl project in Eclipse 4.6 (neon)". https://sourceforge.net/p/e-p-i-c/bugs/691/ Any chance this BUG can be merged into the production version?
I had a similar issue. Switching to the testing version (0.7.5) resolved the following problem: "http://www.epic-ide.org/updates/testing" Error trying to create a new Perl project. Fresh install of Eclipse: Eclipse IDE for Java Developers Version: Oxygen.2 Release (4.7.2) Build id: 20171218-0600 Host OS: macOS Sierra (Version 10.2.6) Action: File / New / Perl Project Immediate error: Plug-in "org.epic.perleditor" was not able to instantiate class "org.epic.core.PerlProjectResourceWizard."
Plug-in "org.epic.perleditor" was not able to instantiate class "org.epic.core.PerlProjectResourceWizard.".
I tried the above workaround. In eclipse-workspace.metadata.plugins\org.epic.debug\dumpvar_epic.pm The change I made was: ... sub _dump_entity { local $\ = undef; ... I am still getting the same error "An error occurred while dumping Perl internal variables; contents of the Variables view may become invalid" I want the variable values to be displayed with their current values as shown in the attached image. What is the permenant solution for this?
Debugging session stucks: recv() is deprecated on :utf8 handles
Thanks for reporting. Fixed in EPIC 0.7.5.
Hello Everyone, I am not an expert in Eclipse - Epic. I need to find a solution to create a perl application server. I would like to create a development environment which is able to contain perl project on an other server. This project should be contain the epic_links. And I would like to connect to this server with an Eclips client. I have tried a Remote System exp. but its really slow through sftp (I have big project). Do you have idea to create a development application server? Thanks' Karol...
Are you sure EPIC is using the edited versions of the files? For dumpvar_epic.pm, you need to edit the version contained inside of the org.epic.debug...jar file in your eclipse's plugins (or dropins) directory. For perl5db.pl it looks up the file via @INC, then patches it, and uses the patched one (it happens at every execution). You may have to put the fixed version in a directory in front of the include path of your project so as to be picked up instead of the default one (this may also work as...
I try both but no lucky :(
Hi All, i'm using EPIC 0.7.4 but i'm not able to debug because the breakpoint doesn't work. I don't know why they are not working, since some time ago they was working perfectly. Recently i update to PERL to version 5.26.1 and they stop to work, maybe the two are correlated. I'm using cygwin, could someone help? Thank you very much
Maybe it's the issue described in https://sourceforge.net/p/e-p-i-c/bugs/698/ - can you test if one the solutions works?
Hi All, i'm using EPIC 0.7.4 but i'm not able to debug because the breakpoint doesn't work. I don't know why they are not working, since some time ago they was working perfectly. Recently i update to per to version 5.26.1 and they stop to work, maybe the two are correlated. I'm using cygwin, could someone help? Thank you very much
Receiving the most effective give In order to receive the best deal on wrinkles cream, keep away from the things that happen to be closely marketed on tv or maybe in glossy magazines. Every time they invest a great deal on their own own marketing spending plan, they cannot supply the finest value. If there's a higher profile representative or perhaps a designer title throughout the label, you can expect to pay out much more, having said that, you won have extra. Celebs hardly ever make use of the...
Debugging session stucks: recv() is deprecated on :utf8 handles
Eclipse IDE for Java Developers 4.5.0.20150621-1200 EPIC 0.6.57 org.epic.feature.main.feature.group Epic Project I see the same symtoms John Arnold reported. I tried to explore the root cause: The communication between Eclipse and Perl (cygwin perl 5.26 version) is using a socket. The messages sent by Eclipse to Perl (perl5db.pl) are catched by the recv() function using the socket handle. With Perl 5.26 a handle using utf-8 layer is not allowed anymore with recv() function. Initially the socket is...
Perlcritic not reporting errors. Silent fail.
Receiving the most effective give In order to receive the best deal on wrinkles cream, keep away from the things that happen to be closely marketed on tv or maybe in glossy magazines. Every time they invest a great deal on their own own marketing spending plan, they cannot supply the finest value. If there's a higher profile representative or perhaps a designer title throughout the label, you can expect to pay out much more, having said that, you won have extra. Celebs hardly ever make use of the...
(Ctrl-F) Find/Replace does not work under Eclipse 4.7 (Oxygen )
Looks like you need 0.7.4 or better for Oxygen: http://e-p-i-c.sf.net/updates/testing
Looks like you need 0.7.4 or better for Oxygen
Given that Oxygen only works with the 0.7.4 and above versions ... should this same change be made added to the 0.6 line, or alternatively allow 0.7.4 to be found at the "main line update site": http://e-p-i-c.sf.net/updates
Receiving the most effective give In order to receive the best deal on wrinkles cream, keep away from the things that happen to be closely marketed on tv or maybe in glossy magazines. Every time they invest a great deal on their own own marketing spending plan, they cannot supply the finest value. If there's a higher profile representative or perhaps a designer title throughout the label, you can expect to pay out much more, having said that, you won have extra. Celebs hardly ever make use of the...
Receiving the most effective give In order to receive the best deal on wrinkles cream, keep away from the things that happen to be closely marketed on tv or maybe in glossy magazines. Every time they invest a great deal on their own own marketing spending plan, they cannot supply the finest value. If there's a higher profile representative or perhaps a designer title throughout the label, you can expect to pay out much more, having said that, you won have extra. Celebs hardly ever make use of the...
Eclipse Neon, Strawberry Perl 5.26.0.1 (May 2017), PadWalker 2.2 installed Symptoms: Simple script to test debug. Start debug, perspective opens and breaks at 1st line. Hit Resume, break stays on 1st line Hit resume again, executes next line of code yet stays on 1st line. Resume icon deemphasised - cannot continue Note no variables displayed in Variables pane
Receiving the most effective give In order to receive the best deal on wrinkles cream, keep away from the things that happen to be closely marketed on tv or maybe in glossy magazines. Every time they invest a great deal on their own own marketing spending plan, they cannot supply the finest value. If there's a higher profile representative or perhaps a designer title throughout the label, you can expect to pay out much more, having said that, you won have extra. Celebs hardly ever make use of the...
eclipse oxygen: stacktrace with org.epic.perleditor.commands.clearMarks undefined
can confirm: works on a fresh install of oxygen javascript and we developer edition. Thank you Jan!
Closing, confirmed as fixed in testing 0.7.4.
Editor does not work in eclipse oxygen
Just released testing 0.7.4 supposedly fixes this problem, but I could not check myself (Oxygen installer crashing for me).
There's a workaround: Get the missing class from the former Eclipse version, it''s placed in org.eclipse.jface_*.jar. Afterwards find your local installation of org.epic.perleditor_0.7.3.jar and add the missing class into that jar, using the correct dir structure for the class like the EPIC classes itself. It just needs to be present and seems to be the only missing class. Afterwards this concrete editor problem was gone for me. Placing the class in some other class path outside that jar didn't work...
Thanks Its Work Again!
I have Also That problem. If i open perl document i became this error: Problems occurred when invoking code from plug-in: "org.eclipse.jface". Exception Stack Trace java.lang.NullPointerException at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.internalFixContext(PartServiceImpl.java:449) at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.bringToTop(PartServiceImpl.java:410) at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.showPart(PartServiceImpl.java:1187) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:3261)...