11:26 p.m.
Hey folks,
once agian, Im not ure this qualifies as a bug, but I can't figure out
how to fix it on my own.
running xemacs21.4.14 on debian-sid(unstable)
After a certain amount of fiddling with locales and keymaps, I've
managed to get accented characters to work right in almost
everything. I can type, for instance, u-umlaut or a-accent-grave
atthe bash prompt, in mozilla, and in openoffice without a problem.
In xemacs, these characters display properly all the time. At the
console and in its own X window (that is, frame), I can also type
accented characters without any difficulty. However, I mostly run
xemacs with the -nw switch -- for writing emails and also when taking
notes on my underpowered laptop. when run within a terminal, xemacs
does *not* recognize accented characters when I type them in (though
it displays them just fine). Instead, for instance, it interprets
'u-umlaut' as'M-I,' which is bound to 'shell-command-on-region'.
iso-accents-mode is a partial fix for this problem, but it doesn't
always work and anyway, it's not nearly as convenient as a
single-keystroke solution. Is there a way to fix this?
Thanks as ususal,
matt
12:01 a.m.
Matt Price <matt.price(a)utoronto.ca> writes:
In xemacs, these characters display properly all the time. At the
console and in its own X window (that is, frame), I can also type
accented characters without any difficulty. However, I mostly run
xemacs with the -nw switch -- for writing emails and also when taking
notes on my underpowered laptop. when run within a terminal, xemacs
does *not* recognize accented characters when I type them in (though
it displays them just fine).
[...]
Is there a way to fix this?
(set-input-mode nil nil 'please-leave-8-bit-chars-alone-thankyouverymuch)
Obvious, isn't it? :-)
2:10 a.m.
New subject: SUCCESS -- accented characters!
On Sun, Nov 30, 2003 at 01:01:55AM +0100, Hrvoje Niksic wrote:
Matt Price <matt.price(a)utoronto.ca> writes:
> In xemacs, these characters display properly all the time. At the
> console and in its own X window (that is, frame), I can also type
> accented characters without any difficulty. However, I mostly run
> xemacs with the -nw switch -- for writing emails and also when taking
> notes on my underpowered laptop. when run within a terminal, xemacs
> does *not* recognize accented characters when I type them in (though
> it displays them just fine).
[...]
> Is there a way to fix this?
(set-input-mode nil nil 'please-leave-8-bit-chars-alone-thankyouverymuch)
Obvious, isn't it? :-)
Thank you thank you!! can't tell you how much this improves my life!
matt
2:34 p.m.
Hrvoje Niksic <hniksic(a)xemacs.org> さんは書きました:
Matt Price <matt.price(a)utoronto.ca> writes:
> In xemacs, these characters display properly all the time. At the
> console and in its own X window (that is, frame), I can also type
> accented characters without any difficulty. However, I mostly run
> xemacs with the -nw switch -- for writing emails and also when taking
> notes on my underpowered laptop. when run within a terminal, xemacs
> does *not* recognize accented characters when I type them in (though
> it displays them just fine).
[...]
> Is there a way to fix this?
(set-input-mode nil nil 'please-leave-8-bit-chars-alone-thankyouverymuch)
Obvious, isn't it? :-)
This still doesn't work for me. In my case 'current-input-mode
returns
(nil nil t ?\^G)
i.e. I have the above setting, nevertheless I cannot input German
umlauts into "xemacs -nw" running in an xterm or mlterm, although
they display fine.
Does this depend on the locale? I'm using ja_JP.UTF-8.
--
Mike FABIAN <mfabian(a)suse.de> http://www.suse.de/~mfabian
睡眠不足はいい仕事の敵だ。
2:51 p.m.
Mike FABIAN <mfabian(a)suse.de> writes:
> (set-input-mode nil nil
'please-leave-8-bit-chars-alone-thankyouverymuch)
>
> Obvious, isn't it? :-)
This still doesn't work for me. In my case 'current-input-mode
returns
(nil nil t ?\^G)
i.e. I have the above setting
No you don't, at least not necessarily. Contrary to appearances, the
third argument to set-input-mode is not boolean. According to the
docstring, Its meaning is:
nil -- ignore 8th bit altogether
t -- interpret 8th bit as the meta modifier (the default)
anything else -- just insert 8-bit chars without interpreting them specially.
That is why my example used a funny symbol rather than just t.
3:16 p.m.
Hrvoje Niksic <hniksic(a)xemacs.org> さんは書きました:
Mike FABIAN <mfabian(a)suse.de> writes:
>> (set-input-mode nil nil 'please-leave-8-bit-chars-alone-thankyouverymuch)
>>
>> Obvious, isn't it? :-)
>
> This still doesn't work for me. In my case 'current-input-mode
> returns
>
> (nil nil t ?\^G)
>
> i.e. I have the above setting
No you don't, at least not necessarily. Contrary to appearances, the
third argument to set-input-mode is not boolean. According to the
docstring, Its meaning is:
nil -- ignore 8th bit altogether
t -- interpret 8th bit as the meta modifier (the default)
anything else -- just insert 8-bit chars without interpreting them specially.
That is why my example used a funny symbol rather than just t.
Thank you, I see. It still doesn't help much in UTF-8 though, now I
get U+00C3 and U+00B6 inserted when I type a German 'ö'. I.e. the
UTF-8 representation is inserted directly.
--
Mike FABIAN <mfabian(a)suse.de> http://www.suse.de/~mfabian
睡眠不足はいい仕事の敵だ。
3:36 p.m.
Mike FABIAN <mfabian(a)suse.de> writes:
Thank you, I see. It still doesn't help much in UTF-8 though, now
I
get U+00C3 and U+00B6 inserted when I type a German 'ö'.
I see. Theoretically the keyboard coding system
(set-keyboard-coding-system) should be used for this (along with
UCS-Mule to provide support for UTF-8 coding in the first place), but
that's always been flagged as "broken".
I.e. the UTF-8 representation is inserted directly.
It pains me to even suggest it, but I suppose you could bind the
appropriate several key sequences to commands that merely insert the
German umlauts.
7658
days inactive
7664
days old
6 comments
3 participants
participants (3)
-
Hrvoje Niksic -
Matt Price -
Mike FABIAN