On Mon, 22 Apr 2002 21:07:28 +0200 wrote Joachim Schmitz
<js@xxxxxxxxxxxxx>:
>> I just upgraded my system to SuSE 8.0, and now 8bit chars don't work
>> anymore in jed. I use jed 0.99.15 in rxvt window. This only affects
>> jed. On the commandline it works ok. Any hint is welcome.
> 1. this is true for the console also, and all xterms I could get hold
> of. 2. It is "only" a display problem, I can enter umlauts with jed. I
> only don't see them in jed.
It is a display only problem. My jed seams not to display all chars with
an ascii value above 127. When I do a describe keybindings. All keys
are there, one just does not see them. If I just cut and paste the
invisible lines into a text-file and cat that to the screen I see the
key-definitions. So what does my jed prevent from displaying chars above
127 ?
On Tue, 23 Apr 2002 08:10:08 +0200 wrote Jens.Wulf@xxxxxxxxxxxxxxxx:
# ifdef IBMPC_SYSTEM
% DISPLAY_EIGHT_BIT = 128;
# else
% DISPLAY_EIGHT_BIT = 160; % Other systems assume ISO Latin 1
# endif
Seems like the most obvious. (You can test the current setting with
Help>Describe_Variable: DISPLAY_EIGHT_BIT)
Second hint: (ugly) When I upgraded to SuSE 7.3, my xjed showed a very
strange behaviour: characters and cursor were out of sync: (every
self_insert let the cursor jump 2 places) the buffer looked totally weird.
I supposed that might have to do with unicode support (but never found
out) and just compiled new from the source rpm. This solved my problem.
(I know, this sounds a lot like the typical windowish: "just reinstall" I
really don't like, but at least it helped)