unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dani Moncayo <dmoncayo@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Juanma Barranquero <lekktu@gmail.com>, 12082@debbugs.gnu.org
Subject: bug#12082: 24.1.50; Wrong character showed by "C-h c"
Date: Sun, 29 Jul 2012 23:44:18 +0200	[thread overview]
Message-ID: <CAH8Pv0jf6R1=wUYKz-eojfnWsQrOUS3kY2g_8jxiJJkJ1u=U-A@mail.gmail.com> (raw)
In-Reply-To: <83d33eh10q.fsf@gnu.org>

>> With the current Emacs trunk, and from "emacs -Q", if I type "C-h c
>> M-ç", I get the message "M-‡ is undefined" in the echo area.
>>
>> The correct message would be "M-ç is undefined", which is what I get
>> if I repeat the experiment with the Emacs 24.1 release.
>
> This subtlety is the result of (not entirely correct) fix for
> non-ASCII display on TTY.  Should be fixed now (trunk version 109272).

I've update my trunk branch (I have bzr revno 109274) and rebuilt Emacs.

Now I observe these messages from "Emacs -Q":
* C-h c M-ç => "M-‡ is undefined". (wrong, as before)
* C-h c ESC ç => "M-g (translated from <escape> ç) is undefined".
(wrong, should be "M-ç ...")

And from "Emacs -Q -nw":
* C-h c M-ç => "M-ç is undefined" (correct).
* C-h c ESC ç => "M-g (translated from <escape> ç) is undefined"
(wrong, as in the GUI session).


Juanma, could you please test this, and tell if you see the same?

Thanks.

-- 
Dani Moncayo





  reply	other threads:[~2012-07-29 21:44 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-29 17:50 bug#12082: 24.1.50; Wrong character showed by "C-h c" Dani Moncayo
2012-07-29 18:31 ` Eli Zaretskii
2012-07-29 21:44   ` Dani Moncayo [this message]
2012-07-29 23:04     ` Juanma Barranquero
2012-07-30  3:37       ` Eli Zaretskii
2012-07-30  9:17         ` Dani Moncayo
     [not found]         ` <CAAeL0SS+PoA8X_FY6DWO1bqEn9NJJNm23Dn=5mdXZxAcKmVmYQ@mail.gmail.com>
2012-07-30 14:32           ` Eli Zaretskii
2012-07-30 14:49             ` Juanma Barranquero
2012-07-30 14:53             ` Dani Moncayo
2012-07-30 14:56               ` Juanma Barranquero
2012-07-30 15:05               ` Dani Moncayo
2012-07-30 15:58                 ` Eli Zaretskii
2012-07-30 16:16                   ` Dani Moncayo
2012-07-30 16:43                     ` Eli Zaretskii
2012-07-30 17:16                       ` Eli Zaretskii
2012-07-30 17:47                         ` Dani Moncayo
2012-07-30 18:11                           ` Eli Zaretskii
     [not found]                             ` <CAH8Pv0jk4Wv1WGFwtvmh0G76dTH6ae9kzPfmSb4Hgtyo4ry2GQ@mail.gmail.com>
2012-07-30 18:18                               ` Dani Moncayo
2012-07-30 19:12                                 ` Eli Zaretskii
2012-07-30 14:22     ` Dani Moncayo
2012-07-30 14:32       ` Juanma Barranquero
2012-07-30 14:37       ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAH8Pv0jf6R1=wUYKz-eojfnWsQrOUS3kY2g_8jxiJJkJ1u=U-A@mail.gmail.com' \
    --to=dmoncayo@gmail.com \
    --cc=12082@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=lekktu@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).