Perltidy does not work

quarf wrote on Fri Oct 13 13:07:01 MEST 2006:

Source formatting does not have any effect. Perltidy is correctly installed
via apt on ubuntu.
I'm using Eclipse 3.1.2 and EPIC 0.5.

Any hints?

jgangemi wrote on Fri Oct 13 15:39:08 MEST 2006:
try upgrading to the latest version - 0.5 is quite old at this point.
quarf wrote on Sun Oct 15 12:07:28 MEST 2006:

sorry, I did not mention the full version number of EPIC in my last post.
In fact I'm using EPIC 0.5.14 from
Is there any newer version available?
jploski wrote on Sun Oct 15 12:14:21 MEST 2006:
EPIC comes with its own version of perltidy (as of today), so the fact that
you have a system-wide installation does not matter.

Have you looked into the error log yet?
quarf wrote on Tue Oct 17 07:25:38 MEST 2006:
I'm sorry having to admit that I did not look into the error log. Can you
help me with the path where I find it?
jgangemi wrote on Tue Oct 17 15:52:05 MEST 2006:
there is an eclipse view that will display it. if you don't see the view
(it's in one of the pde folders), then you don't have pde development enabled
in your prefererences. 

go enable it and you'll have access to the error log. you can also find
the log in the .metadata directory of your workspace - it's a .log file.
quarf wrote on Tue Oct 17 17:16:13 MEST 2006:
thank you for the hint.
I found the log file but it does not seem to be very helpful for me.
You can find the part of the log wich is created by Source->Format here:
jploski wrote on Tue Oct 17 19:23:52 MEST 2006:
The error in your .log means that the Perl interpreter closes its end of
the stream while EPIC is still writing (source code to be formatted) to

In order to obtain further information:

cd $WORKSPACE/.metadata/.plugins/org.epic.perleditor/perlutils/perltidy

Then run the exact command line which appears in the .log and see if you
get any errors.

If the above works, the next thing you should try is running Eclipse using
the version of Java from Sun (not gcj).

Perhaps you can also provide the source file which causes the problem, so
I could attempt to reproduce it.
quarf wrote on Wed Oct 18 08:16:45 MEST 2006:
running the command I got this error: "Can't open perl script "perltidy":
No such file or directory".
In fact there is no file in the directory. I created a symlink to /usr/bin/perltidy
where my global installation of perltidy is.
Sourceformatting works fine now.
Because I don't know what went wrong in my case: Do you want any further
information to reproduce the problem?
jploski wrote on Wed Oct 18 18:50:16 MEST 2006:
EPIC is supposed to be extracting 'perltidy' (together with the accompanying
module Perl/ to this directory whenever you run the source formatter
(if these files don't yet exist).

It would be interesting to find out why this does not (did not?) happen
in your case - issues with file/directory ownership or permissions perhaps?
Anyway, the failure to extract the scripts should result in additional messages
in the .log (possibly preceding the one you quoted).

You can try deleting (or moving away) the whole $WORKSPACE/.metadata/.plugins/org.epic.perleditor/perlutils
directory. It should be recreated, together with perltidy, when you run
the formatter.
claudio_sf wrote on Mon Oct 23 09:55:21 MEST 2006:
Same problem here.

Ubuntu 6.06 x64 with epic 3.2.1 (from, not ubuntu) with epic

The directory $WORKSPACE/.metadata/.plugins/org.epic.perleditor/perlutils
is not created, so no plugins are installed.

I am downloading eclipse 3.1 to check if the bugs exists there. If it doesnt,
I will post a bug report.

claudio_sf wrote on Mon Oct 23 11:39:50 MEST 2006:
Eclipse 3.1 works fine with epic 0.4.0, while epic and eclipse 3.2.1 seems
to be broken.  I will file a bug report.

claudio_sf wrote on Mon Oct 23 11:44:19 MEST 2006:
I don't seem able to report a bug (No member of project).

Could not extract resources to directory /home/cra/src/.metadata/.plugins/org.epic.perleditor/perlutils;
please report this as a bug in EPIC /home/cra/src/.metadata/.plugins/org.epic.perleditor/perlutils/perltidy/perltidy
(No such file or directory)
at org.epic.core.util.ResourceUtilities.extractZipEntry(
at org.epic.core.util.ResourceUtilities.extractResources(
at org.epic.core.util.ScriptExecutor.extractScripts(
at org.epic.core.util.ScriptExecutor.getWorkingDir(
at org.epic.perleditor.editors.util.SourceFormatter.format(
at org.epic.perleditor.editors.util.SourceFormatter.format(
at org.epic.perleditor.actions.FormatSourceAction.doRun(
at org.eclipse.jface.action.Action.runWithEvent(
at org.eclipse.ui.actions.RetargetAction.runWithEvent(
at org.eclipse.ui.internal.WWinPluginAction.runWithEvent(
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(
at org.eclipse.jface.action.ActionContributionItem.access$2(
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(
at org.eclipse.swt.widgets.EventTable.sendEvent(
at org.eclipse.swt.widgets.Widget.sendEvent(
at org.eclipse.swt.widgets.Display.runDeferredEvents(
at org.eclipse.swt.widgets.Display.readAndDispatch(
at org.eclipse.ui.internal.Workbench.runEventLoop(
at org.eclipse.ui.internal.Workbench.runUI(
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(
at org.eclipse.core.internal.runtime.PlatformActivator$
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(
at java.lang.reflect.Method.invoke(
at org.eclipse.core.launcher.Main.invokeFramework(
at org.eclipse.core.launcher.Main.basicRun(
at org.eclipse.core.launcher.Main.main(

java.fullversion=GNU libgcj 4.1.0 (Ubuntu 4.1.0-1ubuntu8)
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_GB
Command-line arguments:  -os linux -ws gtk -arch x86_64

Note: The above is an archived snapshot of a forum thread. Use the original thread at to post comments.