From: Eli Zaretskii <eliz@gnu.org>
To: Dani Moncayo <dmoncayo@gmail.com>
Cc: lekktu@gmail.com, 12082@debbugs.gnu.org
Subject: bug#12082: 24.1.50; Wrong character showed by "C-h c"
Date: Mon, 30 Jul 2012 19:43:08 +0300 [thread overview]
Message-ID: <83haspfbdv.fsf@gnu.org> (raw)
In-Reply-To: <CAH8Pv0iQ3PXNYBdeEi9omWoTUR2v57ykcCEG93-q=9UAbmrvzg@mail.gmail.com>
> Date: Mon, 30 Jul 2012 18:16:08 +0200
> From: Dani Moncayo <dmoncayo@gmail.com>
> Cc: lekktu@gmail.com, 12082@debbugs.gnu.org
>
> >> > [M-ç]
> >> > warning: w32term: 0xffffff87 => 0x2021 (cp1252)
> >> >
> >> > (yes, only one message for this character)
> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > This means M-ç gets processed by some code in w32fns.c that doesn't
> > have a DebPrint. Can you find out which one (by sticking DebPrint)?
> > For example, these two fragments look as possible suspects:
> >
> > 1)
> > default:
>
> In this line, I inserted this: DebPrint (("w32fns: #1-default 0x%x\n", wParam));
>
> > /* If not defined as a function key, change it to a WM_CHAR message. */
> > if (wParam > 255 || !lispy_function_keys[wParam])
>
>
> And I've seen that the execution arrives to this first case. This is
> the output from gdb:
>
> warning: w32fns: #1-default 0xbf
> warning: w32term: 0xffffff87 => 0x2021 (cp1252)
Heh, everything is clear now. Stay tuned for a solution.
Thanks.
next prev parent reply other threads:[~2012-07-30 16:43 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
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 [this message]
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=83haspfbdv.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=12082@debbugs.gnu.org \
--cc=dmoncayo@gmail.com \
--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).