newbie, BeanShell error, emacs emulation, WinXP

Submitted by gap on Monday, 28 September, 2009 - 22:49

I'm trying out jEdit as a possible 21st Century replacement for XEmacs to write python code. By now my fingers are hard-wired with Emacs keybindings, so I installed Brian's Emacs Emulation Package on two different WinXP machines. On one it works just fine. On the other I get a BeanShell error when jEdit starts (text below). I've reinstalled jEdit and the Emacs Package, updated java, and rebooted, but I still get this error. I'm utterly java illiterate, but it does look like it's failing on the very first line of emacs_bindings.bsh, so I suspect some installation problem. My java is:
Java(TM) SE Runtime Environment (build 1.6.0_15-b03)

Please help ?!
-gap

------------------------------------------------------------
Sourced file: C:\Documents and Settings\Gary\.jedit\startup\emacs_bindings.bsh : Class: bsh.ClassIdentifier not found in namespace : at Line: 26 : in file: print : bsh .ClassIdentifier

Called from method: print : at Line: 8 : in file: C:\Documents and Settings\Gary\.jedit\startup\emacs_bindings.bsh : print ( "in emacs_bindings.bsh" )
at org.gjt.sp.jedit.bsh.BSHAmbiguousName.toClass(BSHAmbiguousName.java:74)
at org.gjt.sp.jedit.bsh.BSHType.getType(BSHType.java:154)
at org.gjt.sp.jedit.bsh.BSHBinaryExpression.eval(BSHBinaryExpression.java:63)
at org.gjt.sp.jedit.bsh.BSHPrimaryExpression.eval(BSHPrimaryExpression.java:102)
at org.gjt.sp.jedit.bsh.BSHPrimaryExpression.eval(BSHPrimaryExpression.java:47)
at org.gjt.sp.jedit.bsh.BSHUnaryExpression.eval(BSHUnaryExpression.java:58)
at org.gjt.sp.jedit.bsh.BSHBinaryExpression.eval(BSHBinaryExpression.java:123)
at org.gjt.sp.jedit.bsh.BSHBinaryExpression.eval(BSHBinaryExpression.java:52)
at org.gjt.sp.jedit.bsh.BSHIfStatement.evaluateCondition(BSHIfStatement.java:63)
at org.gjt.sp.jedit.bsh.BSHIfStatement.eval(BSHIfStatement.java:46)
at org.gjt.sp.jedit.bsh.BSHBlock.evalBlock(BSHBlock.java:130)
at org.gjt.sp.jedit.bsh.BSHBlock.eval(BSHBlock.java:80)
at org.gjt.sp.jedit.bsh.BshMethod.invokeImpl(BshMethod.java:362)
at org.gjt.sp.jedit.bsh.BshMethod.invoke(BshMethod.java:258)
at org.gjt.sp.jedit.bsh.BshMethod.invoke(BshMethod.java:186)
at org.gjt.sp.jedit.bsh.Name.invokeLocalMethod(Name.java:955)
at org.gjt.sp.jedit.bsh.Name.invokeMethod(Name.java:801)
at org.gjt.sp.jedit.bsh.BSHMethodInvocation.eval(BSHMethodInvocation.java:75)
at org.gjt.sp.jedit.bsh.BSHPrimaryExpression.eval(BSHPrimaryExpression.java:102)
at org.gjt.sp.jedit.bsh.BSHPrimaryExpression.eval(BSHPrimaryExpression.java:47)
at org.gjt.sp.jedit.bsh.Interpreter.eval(Interpreter.java:644)
at org.gjt.sp.jedit.BeanShell._runScript(BeanShell.java:331)
at org.gjt.sp.jedit.BeanShell._runScript(BeanShell.java:279)
at org.gjt.sp.jedit.BeanShell.runScript(BeanShell.java:205)
at org.gjt.sp.jedit.Macros$BeanShellHandler.runMacro(Macros.java:1030)
at org.gjt.sp.jedit.jEdit.runStartupScripts(jEdit.java:3704)
at org.gjt.sp.jedit.jEdit.main(jEdit.java:511)

console plugin needed

by xhornet on Wed, 18/08/2010 - 00:59

I also have this problem when install jedit on a new machine, but after I install plugin "console", the problem is gone.
I am using Windows XP, and I found after install console plugin, there is one jar named "Console.jar" under "C:\Documents and Settings\$MYLOGINID\.jedit\jars", and print.bsh is in that jar "Console.jar\console\bsh\print.bsh"
I hope this can solve your problem.

Different installations

by Robert Schwenn on Wed, 28/10/2009 - 18:48

Since the script is running well on one Machine You should find the differences between them:

- version of jEdit
- version of Java (which is used by jEdit, see help->about)
- installed plugin's

Also, You could check if the settings are relevant by starting with standard settings (delete resp. rename the settings directory). Therefore You could copy the emacs_bindings.bsh to the settings directory in jEdit's program directory.

If You can't find anything, just copy the working jEdit installation from one machine to the other...

Robert

Me too

by vaper on Fri, 23/10/2009 - 17:28

I'm getting exactly the same error:
Class: bsh.ClassIdentifier not found in namespace : at Line: 26 : in file: print : bsh .ClassIdentifier
with "print" called from "exec()"

It's in a script that works perfectly on my local machine, and has for years. But, running it on a remote machine, I'm getting this error. The remote machine has java 1.5.0_12

Maybe something about the java installation...

Mine's fixed...

by vaper on Wed, 28/10/2009 - 15:40

Looks like my solution won't work for you; I was doing exec(cscript.exe...) and it seems that cscript on the remote machine, unlike my local machine, was returning something -- causing exec() to print(), giving the error. Stopping cscript from returning anything solved my problem. But you explicitly want to print()...

file	ver	dls
GdbPlugin for jEdit 4.5+	0.5	1154
Hypersearch results analysis	1.0	2239
German Language Pack for jEdit 5 (up-to-date)	5.3	4148
Goal column macros	1.0	4035
Hyper-search all .txt files in home dir	1	3291
Select line	1.0	3451
Open_Copied_Path.bsh	1.0	8505
Select_All_or_Lines.bsh	1.0	3416
A BeanShell macro script to search and open a recent file or a file in the current directory.	1.0	5639
Select contents in between parentheses (excluding parentheses)	1.0	3546

file	ver	dls
German Localization light	4.4.2.1	101634
Context Free Art (*.cfdg)	0.31	46062
BBEdit scheme	1.0	18601
JBuilder scheme	.001	18502
ColdFusion scheme	1.0	18031
R Edit Mode - extensive version	0.1	17481
Advanced HTML edit mode	1.0	16213
Matlab Edit Mode	1.0	16075
jEdit XP icons	1.0	15236
XP icons for jEdit	1.1	14300

RSS

XML

HTML

« November 2024
Mo	Tu	We	Th	Fr	Sa	Su
				1	2	3
4	5	6	7	8	9	10
11	12	13	14	15	16	17
18	19	20	21	22	23	24
25	26	27	28	29	30