Bug with Console plugin 4.3.7, jEdit 4.3pre14 for Windows, and the font White Rabbit
Submitted by Friday, 4 July, 2008 - 01:16
on
OK, hell of a combination, I know. But, here we go.
I recently (ie within the last few months) upgraded to pre14. As usual, Console was docked at the bottom of the screen. I had set the font to White Rabbit several months previously, and had no issues. I had been using pre9.
I had just finished writing some C, and wanted to run gcc (yes, on Windows). So, I brought up the Console.
I got the following image:
The same happened with the Beanshell drop-down. As a result of this, I couldn't do anything with Console.
Why, you ask? Because it wouldn't accept any input. I mashed keys for a few minutes when I realised this, but to no avail.
Today, I checked if there was an update to jEdit, then decided to bring this matter to the fore. In so doing, I checked the settings for Console. I changed the font, then opened it.
And it worked.
I have no idea if this is a Console bug, a pre14 bug, or a "feature" of the font itself. I'm assuming it's a pre14, but it could be a Console + pre14 bug, ie a Console bug that only occurs in pre14 (and yes, that could be considered a pre14 bug).
Any
I recently (ie within the last few months) upgraded to pre14. As usual, Console was docked at the bottom of the screen. I had set the font to White Rabbit several months previously, and had no issues. I had been using pre9.
I had just finished writing some C, and wanted to run gcc (yes, on Windows). So, I brought up the Console.
I got the following image:
The same happened with the Beanshell drop-down. As a result of this, I couldn't do anything with Console.
Why, you ask? Because it wouldn't accept any input. I mashed keys for a few minutes when I realised this, but to no avail.
Today, I checked if there was an update to jEdit, then decided to bring this matter to the fore. In so doing, I checked the settings for Console. I changed the font, then opened it.
And it worked.
I have no idea if this is a Console bug, a pre14 bug, or a "feature" of the font itself. I'm assuming it's a pre14, but it could be a Console + pre14 bug, ie a Console bug that only occurs in pre14 (and yes, that could be considered a pre14 bug).
Any