Bug#435452: emacs22: `set-keyboard-coding-system' fails in non-X11 mode]
Hi, Stefan Monnier [EMAIL PROTECTED] writes: Typing M-x yields the `ø' (o slash) character instead of running `execute-extended-command'. This is because your terminal sends the exact same byte sequence (in this case it's actually a single byte) when you type M-x as when you type ø, so Emacs has no way to distinguish the two: it chooses to interpret the byte as ø here (which messes up the M-x case) and you could tell it to interpret it as M-x (which would mess up the ø case). I see, thanks for the clarification! Indeed, that's the right solution because it tells your Terminal to use different byte-sequences for the two different cases. Understood. Thanks, Ludovic.
Bug#435452: emacs22: `set-keyboard-coding-system' fails in non-X11 mode]
Typing M-x yields the `ø' (o slash) character instead of running `execute-extended-command'. This is because your terminal sends the exact same byte sequence (in this case it's actually a single byte) when you type M-x as when you type ø, so Emacs has no way to distinguish the two: it chooses to interpret the byte as ø here (which messes up the M-x case) and you could tell it to interpret it as M-x (which would mess up the ø case). Checking the Meta Sends Escape box of the xterm in which I run Emacs 22 also fixes the problem, even with a non-C locale. Indeed, that's the right solution because it tells your Terminal to use different byte-sequences for the two different cases. Stefan
Bug#435452: emacs22: `set-keyboard-coding-system' fails in non-X11 mode]
Hi, Kenichi Handa [EMAIL PROTECTED] writes: In article [EMAIL PROTECTED], [EMAIL PROTECTED] (Ludovic Courtès) writes: Indeed, using C as my locale fixes the problem (I used to have LC_CTYPE=fr_FR). Strangely enough, Emacs 21.4.1 with LC_CTYPE=fr_FR doesn't have the problem (i.e., dead keys are usable). Does it mean that you have a problem with Emacs 22 with LC_CTYPE=fr_FR? Yes: dead keys (e.g., Meta) won't work. In that locale, emacs -nw should automatically set keyboard-coding-system to latin-1 and the input mode to (t nil 0 7), and thus it should accept latin-1 characters sent from a terminal correctly. What happens when you type some latin-1 character with dead-key method under LC_CTYPE=fr_FR? Typing M-x yields the `ø' (o slash) character instead of running `execute-extended-command'. Typing accented characters with the `latin-1-prefix' input method, for instance, does work, but I'm not sure how this relates to the fact that Meta doesn't work. Checking the Meta Sends Escape box of the xterm in which I run Emacs 22 also fixes the problem, even with a non-C locale. It seems that your Emacs' input mode is set not to accept 8-bit input. Please tell me what is shown by ESC : (current-input-mode) RET = (t nil 0 7) Thanks, Ludovic.
Bug#435452: emacs22: `set-keyboard-coding-system' fails in non-X11 mode]
Hi, Sven Joachim [EMAIL PROTECTED] writes: Invoking `set-keyboard-coding-system' in an emacs -nw session fails. For instance, asking it `no-conversion' (which is needed so that dead keys work as expected) fails: Unsupported coding system in Encoded-kbd mode: no-conversion I don't understand why you have to set keyboard-coding-system to no-conversion for dead keys. Dead keys must be handled by terminal, and Emacs just receives the resulting character (encoded in your locale) from the terminal. So, setting keyboard-coding-system to what is appropriate for your locale should work well, and that should be done automatically. Indeed, using C as my locale fixes the problem (I used to have LC_CTYPE=fr_FR). Strangely enough, Emacs 21.4.1 with LC_CTYPE=fr_FR doesn't have the problem (i.e., dead keys are usable). Checking the Meta Sends Escape box of the xterm in which I run Emacs 22 also fixes the problem, even with a non-C locale. I guess I'm just displaying my lack of familiarity with how terminals work... What other choices were tried? utf-8, latin-X should all work. What is your locale? With a C locale, utf-8, latin-1, and others are accepted, whereas `no-conversion' yields the above error message. Thanks, Ludovic. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#435452: emacs22: `set-keyboard-coding-system' fails in non-X11 mode]
In article [EMAIL PROTECTED], [EMAIL PROTECTED] (Ludovic Court$(D+2(Bs) writes: Hi, Sven Joachim [EMAIL PROTECTED] writes: Invoking `set-keyboard-coding-system' in an emacs -nw session fails. For instance, asking it `no-conversion' (which is needed so that dead keys work as expected) fails: Unsupported coding system in Encoded-kbd mode: no-conversion I don't understand why you have to set keyboard-coding-system to no-conversion for dead keys. Dead keys must be handled by terminal, and Emacs just receives the resulting character (encoded in your locale) from the terminal. So, setting keyboard-coding-system to what is appropriate for your locale should work well, and that should be done automatically. Indeed, using C as my locale fixes the problem (I used to have LC_CTYPE=fr_FR). Strangely enough, Emacs 21.4.1 with LC_CTYPE=fr_FR doesn't have the problem (i.e., dead keys are usable). Does it mean that you have a problem with Emacs 22 with LC_CTYPE=fr_FR? In that locale, emacs -nw should automatically set keyboard-coding-system to latin-1 and the input mode to (t nil 0 7), and thus it should accept latin-1 characters sent from a terminal correctly. What happens when you type some latin-1 character with dead-key method under LC_CTYPE=fr_FR? Checking the Meta Sends Escape box of the xterm in which I run Emacs 22 also fixes the problem, even with a non-C locale. It seems that your Emacs' input mode is set not to accept 8-bit input. Please tell me what is shown by ESC : (current-input-mode) RET I guess I'm just displaying my lack of familiarity with how terminals work... What other choices were tried? utf-8, latin-X should all work. What is your locale? With a C locale, utf-8, latin-1, and others are accepted, whereas `no-conversion' yields the above error message. That is because setting keyboard-coding-system to no-conversion is useless. --- Kenichi Handa [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#435452: emacs22: `set-keyboard-coding-system' fails in non-X11 mode]
Hello Ludovic, I received an answer from Emacs developer Kenichi Handa (quoted below). He says that it should not be necessary to invoke `set-keyboard-coding-system'. Kenichi Handa [EMAIL PROTECTED] writes: In article [EMAIL PROTECTED], Richard Stallman [EMAIL PROTECTED] writes: Would you please DTRT and ack? Ok. --- Start of forwarded message --- To: [EMAIL PROTECTED] From: Sven Joachim [EMAIL PROTECTED] Date: Sun, 26 Aug 2007 11:32:22 +0200 Subject: [Ludovic Courtes] Bug#435452: emacs22: `set-keyboard-coding-system' fails in non-X11 mode I received this via the Debian Bug Tracking System. Handa-san, can you comment on it? [...] Invoking `set-keyboard-coding-system' in an emacs -nw session fails. For instance, asking it `no-conversion' (which is needed so that dead keys work as expected) fails: Unsupported coding system in Encoded-kbd mode: no-conversion I don't understand why you have to set keyboard-coding-system to no-conversion for dead keys. Dead keys must be handled by terminal, and Emacs just receives the resulting character (encoded in your locale) from the terminal. So, setting keyboard-coding-system to what is appropriate for your locale should work well, and that should be done automatically. Other choices fail similarly. What other choices were tried? utf-8, latin-X should all work. What is your locale? --- Kenichi Handa [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#435452: emacs22: `set-keyboard-coding-system' fails in non-X11 mode
Package: emacs22 Version: 22.1+1-1 Severity: normal Hi Rob! Invoking `set-keyboard-coding-system' in an emacs -nw session fails. For instance, asking it `no-conversion' (which is needed so that dead keys work as expected) fails: Unsupported coding system in Encoded-kbd mode: no-conversion Other choices fail similarly. Thanks, Ludovic. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: powerpc (ppc) Kernel: Linux 2.6.21-2-powerpc-smp (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=fr_FR (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages emacs22 depends on: ii emacs22-bin-common 22.1+1-1 The GNU Emacs editor's shared, arc ii libc6 2.6-1GNU C Library: Shared libraries ii libice6 1:1.0.3-2X11 Inter-Client Exchange library ii libjpeg62 6b-13The Independent JPEG Group's JPEG ii libncurses5 5.6-3Shared libraries for terminal hand ii libpng12-0 1.2.15~beta5-2 PNG library - runtime ii libsm6 2:1.0.3-1+b1 X11 Session Management library ii libtiff43.8.2-7 Tag Image File Format (TIFF) libra ii libungif4g 4.1.4-5+b1 shared library for GIF images ii libx11-62:1.0.3-7X11 client-side library ii libxext61:1.0.3-2X11 miscellaneous extension librar ii libxmu6 1:1.0.3-1X11 miscellaneous utility library ii libxpm4 1:3.5.6-3X11 pixmap library ii libxt6 1:1.0.5-3X11 toolkit intrinsics library ii xaw3dg 1.5+E-15 Xaw3d widget set ii zlib1g 1:1.2.3.3.dfsg-4 compression library - runtime emacs22 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
