From: Eli Zaretskii <eliz@gnu.org>
To: Dani Moncayo <dmoncayo@gmail.com>
Cc: 12806@debbugs.gnu.org
Subject: bug#12806: 24.3.50; Dead keys misbehavior when scroll-lock is enabled
Date: Wed, 07 Nov 2012 22:09:30 +0200 [thread overview]
Message-ID: <83k3tx18g5.fsf@gnu.org> (raw)
In-Reply-To: <CAH8Pv0j3b6qSyun2qSJNYH-g7dxLddeOe6NY7Je-=QOmj9d-Ag@mail.gmail.com>
> Date: Wed, 7 Nov 2012 20:45:50 +0100
> From: Dani Moncayo <dmoncayo@gmail.com>
> Cc: 12806@debbugs.gnu.org
>
> > Should be fixed in revision 110822 on the trunk. Please test, as I
> > don't have dead keys on my keyboard to test them myself.
>
> The behavior I see now is the inverse: when scroll-lock is on, Emacs
> does TRT, but when it is off, Emacs fails to manage well the dead key
> (like before when scroll-lock was on).
Sorry, you are on your own, then. The only similar problem I saw
previously on my system is fixed by the changes I committed. There's
something else going on with dead keys, obviously, but without knowing
what's wrong, I cannot fix that. Try stepping through the code around
lines 2973 to 3047 of w32fns.c, and see what is going on there when
you type the dead key and the one after it. If you tell what you see,
maybe I can suggest a solution.
next prev parent reply other threads:[~2012-11-07 20:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-05 19:54 bug#12806: 24.3.50; Dead keys misbehavior when scroll-lock is enabled Dani Moncayo
2012-11-05 20:43 ` Eli Zaretskii
2012-11-05 20:48 ` Dani Moncayo
2012-11-05 20:57 ` Dani Moncayo
2012-11-05 23:28 ` Juanma Barranquero
2012-11-05 23:52 ` Dani Moncayo
2012-11-07 16:51 ` Eli Zaretskii
2012-11-07 19:45 ` Dani Moncayo
2012-11-07 20:09 ` Eli Zaretskii [this message]
2012-11-07 20:34 ` Dani Moncayo
2012-11-07 20:36 ` Dani Moncayo
2012-11-07 21:14 ` Eli Zaretskii
2012-11-07 21:29 ` Dani Moncayo
2012-11-07 21:50 ` Eli Zaretskii
2012-11-07 22:12 ` Dani Moncayo
2012-11-08 3:47 ` Eli Zaretskii
2012-11-06 15:42 ` Juanma Barranquero
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83k3tx18g5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=12806@debbugs.gnu.org \
--cc=dmoncayo@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.