I recently installed new MacOS version (Yosemite) and after that the jEdit stopped to work. The information in dialog box told me that I should install the legacy version of Java 6 (which I refused). First I tried to install newer version instead – Java 8 (hoping that will help…), but the problem stood… So I tried to download newer version of jEdit, but there was only pre-release 5.2pre1 to download that was newer than my current version. After installing it the jEdit is working but not fully. Controlling jEdit via keyboard makes some strange results. Some shortcuts stopped to react, some shortcuts will execute twice and the buffer switcher does not response to keyboard controls (maybe the problem touches more elements in the environment, but I noticed it just with the buffer switcher). That all together makes my work with jEdit much harder. Also the Console plugin (I know there is separate bug report system for plugins, but I believe that this is not the problem of the plugin) hangs after attempt to open it, which makes jEdit useless for developing for me… I am not sure if the problem is in Yosemite, Java 8 or jEdit pre-release (or all in synergy). I can only let you know that there is some problem connected to Yosemite and/or Java 8 and wait and hope there comes a solution in the near future… I would like to help, but I do not know what I should do to tell you more… If you know how to track some more information, please let me know. Thank you!
Please try jEdit the latest daily build. This seems to be a look & feel issue.
This may be a duplicate of 3864 and 3885.
Thank you, all my problems with keyboard were solved by upgrading the jEdit using the latest daily build. But the more painful problem with console retained. Every attempt to open the console plug-in makes the whole jEdit to hang…
(Yes, I know, it is “just a plug-in” – not the part of original jEdit installation (or?), but this is very useful important plug-in and maybe it should be the part of jEdit – without that plug-in I am not able to run external compiler, so my developing possibilities are notably restricted…)
Should I write a new ticket to plug-in bug report central? Because I do not think this is a problem of the plug-in. I upgraded to Java 8 also on my Windows machine to verify the problem and there is no problem with the plug-in. It seems that the problem is just in the Yosemite.
Your console issue sounds like something different. I am closing this one as "duplicate".
I won't be able to reproduce your yosemite issues without a newer mac. I just reverted my 2008 macbook to Mavericks because the upgrade to yosemite made it unusable.
Okay. Should I open new ticket related to Console plug-in?
(Re your 2008 Mac & Yosemite: Sometimes upgrades lead to such behaviour :-( I hope that my Mac will hold on for a couple years – I do not like to change my things, :-) but with technics is it necessary…)
The yosemite related Console issue is mentioned in
https://sourceforge.net/p/jedit/plugin-bugs/1799/ and seems to be caused by
https://sourceforge.net/p/jedit/bugs/3893/
Yes, I think so – I have also an (maybe important) update… (I suspected that this is (probably) not the problem of the Console plug-in.)
JDiff also makes jEdit to hang and this time I noticed unhandled exception in Terminal window (before, in the past, I was executing the jEdit as Mac “native” app so I did not see it and the last time I did not notice it… :-( ):
After this the jEdit hangs no matter if I am attempting to open the JDiff or the Console plugin. (And there might be of course more of them…)
Please try the latest daily build and see if things are working for you now.
Yes, it is working! Thank you very much… :-)