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: 12806@debbugs.gnu.org
Subject: bug#12806: 24.3.50; Dead keys misbehavior when scroll-lock is enabled
Date: Wed, 7 Nov 2012 21:34:53 +0100	[thread overview]
Message-ID: <CAH8Pv0iv0AhZG1MmkXBVi6wT2QK2Posf82KHeRmPUsqkXCWV9Q@mail.gmail.com> (raw)
In-Reply-To: <83k3tx18g5.fsf@gnu.org>

>> 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.

I'll see what can I do, but FWIW, the situation now is much worse than before:
* Scroll lock is a key that is usually set "off"; that explains why no
one noticed this bug until now.
* What is more important: I've just seen that typing `C-M-u' does
nothing on Emacs.  It is as if no key was pressed at all.  If I do
`C-h c C-M-u' the minibuffer stays as if no key was pressed after `C-h
c'.


FWIW:
* This is with bzr revno 110824.
* Your commit at revno 110822 has a typo: the bug number is "12086",
but you wrote "1280".

-- 
Dani Moncayo





  reply	other threads:[~2012-11-07 20:34 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
2012-11-07 20:34           ` Dani Moncayo [this message]
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

  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=CAH8Pv0iv0AhZG1MmkXBVi6wT2QK2Posf82KHeRmPUsqkXCWV9Q@mail.gmail.com \
    --to=dmoncayo@gmail.com \
    --cc=12806@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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).