unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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 23:50:06 +0200	[thread overview]
Message-ID: <83ehk513sh.fsf@gnu.org> (raw)
In-Reply-To: <CAH8Pv0gWi9K_mBnx9o9r7hnfWrKTBGzaZH-iTFJNwshid9RdAg@mail.gmail.com>

> Date: Wed, 7 Nov 2012 22:29:55 +0100
> From: Dani Moncayo <dmoncayo@gmail.com>
> Cc: 12806@debbugs.gnu.org
> 
> > I reverted the previous change and committed a different one, please
> > see if it solves the problems.
> 
> Thanks.  This is what I see now:
> * C-M-u works again, regardless of the scroll-lock setting.
> * The dead keys don't work (same misbehavior already described), also
> regardless of the scroll-lock setting.
> * The caps-lock key doesn't work: letters are written in lowercase,
> regardless of its setting.

The last one works for me just fine.  Are you sure caps-lock does not
work at all, no matter what the state of the various "lock" keys?  If
that only happened when Num Lock was on, then I fixed that in revision
110826.





  reply	other threads:[~2012-11-07 21:50 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
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 [this message]
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=83ehk513sh.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 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).