Activity for Jan Ploski
-
Jan Ploski posted a comment on discussion Help
I suppose this could be achieved by using a wrapper script for the Perl interpreter (the "Perl executable" in EPIC Preferences). The wrapper could check the command line arguments (specifically for -c), set the enviornment variable if compilation is detected, and then invoke the real Perl interpreter.
-
There is no option to avoid running BEGIN blocks. Running these blocks is generally essential for "syntax checking" (actually: reporting compilation errors) to be accurate. If you wish to avoid running certain parts of code in BEGIN block, perhaps you can work around by defining some environment variable (only at actual execution time of the script) and checking for it in inside of the (always executed) BEGIN block.
-
Thanks for the suggestion, but there is very little (almost no) development going on in this project. Also, I do not like "organizations" (but you are of course free to fork and join the organization then).
-
External content assistant
-
A prototype implementation is now included in testing 0.7.9. See description in User's Guide and https://github.com/jploski/epic-ide/blob/testing/org.epic.perleditor/src/org/epic/perleditor/editors/util/ExternalAutoComplete.java
-
External content assistant
-
Do you experience the "breakpoints ignored" issue in "Hello world" or in some more complex situation. The "breakpoint ignored" issue usually comes down to paths of files as expected by EPIC (and as set up for breakpoints when perl -d is launched) and the paths of files as reported by "perl -d" not matching (despite normalization attempts). How Perl reports appears seems to depend on how the modules are included (e.g. use/require with absolute/relative paths or using @INC with module names). You can...
-
You can work around this issue by introducing a custom perl5db.pl which overrides the PERLDB_OPTS environment variable passed down from EPIC (e.g. replacing the ip address by 127.0.0.1). Whenever you start EPIC in debug mode, it copies the perl5db.pl file from your local Perl installation, patches it up and copies the resulting file to $ECLIPSE_WORKSPACE/.metadata/.plugins/org.epic.debug/perl5db.pl. This version is then normally used to run the debugger. But if you copy this patched up perl5db.pl...
-
Maybe the hostname changes when you connect to VPN? What does "hostname" report at command prompt before/after connecting?
-
Have you tried adding an entry which maps your hostname to 127.0.0.1 to the Windows hosts file?
-
"perl debug output displayed on console pane" - perhaps because "Preferences > Perl > Enable debugger console (experimental)" is still enabled?
-
Are we talking about a "Perl Local" or "Perl Remote" launch configuration here? Is 10.0.0.76 the IP of your host? Are you able to listen on 10.0.0.76:5000 and connect to it yourself (you said you can't install netcat, but maybe with a Perl script)?
-
Can't be, the RemotePort must also include an IP address (or at least a colon before the port number). And you should check with netstat -a whether that IP address and port number are being listened on (when you launch the debug session).
-
You can see PERLDB_OPTS by first checking Preferences > Perl > Enable debugger console (experimental). Then when you launch the debug session, an entry is added to the "Error Log" view (if your Eclipse has it) with the perl -d command line and environment variables, among them PERLDB_OPTS. If you don't have Error Log, the same information is written to file ...path-to-workspace/.metadata/.log
-
Take note of the PERLDB_OPTS environment variable passed to the perl -d process when you start the debugging session. In the original poster's example PERLDB_OPTS=RemotePort=192.168.0.101:5000 DumpReused ReadLine=0 This means that the perl -d subprocess will try establishing a TCP connection to 192.168.0.101:5000, which is where the EPIC IDE should be listening for it. Check with netstat -a that the port is indeed being listened to (once you launch a debug session) and that the IP address being listened...
-
I agree - could you examine it more closely and remove the offending view?
-
"Perl Auto Builder" doesn't work anymore with Eclipse 2020-09
-
Fixed in EPIC testing 0.7.8.
-
Garbled utf8 lexical variable names in Variables view
-
perl debugger crashes
-
Have you looked at what's in the perl5db.pl file (which EPIC derives from the one found in your Perl installation by applying a patch)? IIRC, perl5db.pl is overwritten each time when EPIC starts a debugging session, but you can copy it elseswhere and put that directory in front of the project's Perl include path so as to override it with your own version (and then insert into it some commands like debugging output to some file, to understand what's going on around that fatal "line 8675").
-
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.)
-
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.)
-
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.
-
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.
-
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?
-
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.
-
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. 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).
-
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...
-
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 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...
-
Debugging session stucks: recv() is deprecated on :utf8 handles
-
Thanks for reporting. Fixed in EPIC 0.7.5.
-
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...
-
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?
-
Editor does not work in eclipse oxygen
-
Closing, confirmed as fixed in testing 0.7.4.
-
Just released testing 0.7.4 supposedly fixes this problem, but I could not check myself (Oxygen installer crashing for me).
-
Syntax highlighting after __END__
-
Implemented in 0.7.3.
-
Syntax highlighting after __END__
-
Try "Window >Preferences > Perl > Task Tags" instead.
-
If you have control over how the application is started, you can use a wrapper script...
-
EPIC is trying hard to translate the paths reported by the backend "perl -d" process...
-
First off, I suggest that you replace JARs in your dropins folder by those from the...
-
The website issue (IP address change) should be fixed in half an hour from now (when...
-
Basically in perl.g:337 when an open paren after sub keyword is encountered it switches...
-
Your source code doesn't matter (much), you can comment out pretty much everything...
-
FWIW, I tried opening your included script in EPIC 0.7.0 on Debian oldstable (perl...
-
I think you should be able to perform an offline install by putting the following...
-
Because I've had no reasons to take any interest in Perl 6 so far, I can't contribute...
-
The command used to run perlcritic (with default settings) in my test is as follows:...
-
All I can say is that the equivalent Linux variant works: 1 2 3 4#!/bin/bash /usr/bin/perlcritic...
-
The first thing that comes to mind is that you rather than "perl -x" could use a...
-
Whether environment variables are inherited by Eclipse or not depends on how you...
-
EPIC invokes whichever Perl executable you specified via Preferences.
-
Oops, didn't see your screenshot. I see you figured it out.
-
It seems that the debugger backend ("perl -d", perl5db.pl) intercepts and redirects...
-
It happens because the Tk module apparently behaves differently in debug and non-debug...
-
IO::Socket sounds like a good guess, as the debugger backend (perl -d) relies on...
-
I just tried with the current version of EPIC, and it worked for me. So you'd have...
-
Right-click context menu is not relevant to EPIC. Use the pulldown menu activated...
-
I don't think there is anything in EPIC that would trigger this behavior. I recall...
-
I don't think there is anything in EPIC that would trigger this behavior. I recall...
-
I suppose you cannot install normally from the update site? Then maybe try installing...
-
I suppose you cannot install normally from the update site? Then maybe try installing...
-
Please try again, the problem has been fixed.
-
unable to install EPIC editor for Eclipse
-
This problem is now fixed.
-
There is currently a web server misconfiguration (302 Moved reponses instead of 404...
-
There appears to be a misconfiguration of the web server, which is responding to...
-
Not really related to EPIC or Eclipse, but some types of connectivity problems in...
-
The file content.xml referenced in your error message does not exist on the server....
-
I just checked, and it works for me. I suggest unchecking the "Contact all update...
-
Sure, go ahead!
-
Perhaps you can get some clues if you select Window > Preferences > Perl EPIC > Enable...
-
I suggest that you don't rely on any hardcoded "use lib", relative or absolute, at...
-
Here's another tip: it's rather strange to have a relative project include path point...
-
The first thing I would try is create a Hello world Perl project, add whichever path...
-
Change Perl CGI file lookup or settings to load the right file
-
Applied patch http://sourceforge.net/p/e-p-i-c/discussion/258688/thread/f9ba2e1b/#ee55...
-
I tried upgrading ANTLR in EPIC once. Lots of effort. Lots of potential to break...
-
Your patches above seem reasonable and unlikely to break existing configurations....
-
Implemented in Git (patches contributed by Jacob L. Anawalt)
-
Change Perl CGI file lookup or settings to load the right file
-
There is no newer devguide, but your setup sounds just about right and not much has...
-
I'm going to look into it later this week. BTW, for the current version of EPIC you...
-
Template insertion does not honor the project's new text file delimiter
-
Fixed in 0.6.56. You can update now.
-
Fixed on master.
-
Template insertion does not honor the project's new text file delimiter
-
I'm confused by your changes (which comments refer to your old and new project setup...
-
Note that it's safe to delete the "epic_links" project - it will be automatically...
-
What is the absolute path of the module that you think should be opened? What is...
-
What module from which project and what do you mean by "removed"? Do you have perl/lib...
-
Your @INC path is the issue - the pseudoproject epic_links is a way for EPIC to access...
-
You are looking at the right-click context menu instead of at the popup displayed...
1 >