bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#2827: marked as done (Can't use Caps Lock on Windows)


From: Emacs bug Tracking System
Subject: bug#2827: marked as done (Can't use Caps Lock on Windows)
Date: Thu, 29 Oct 2009 14:55:05 +0000

Your message dated Thu, 29 Oct 2009 22:47:22 +0800
with message-id <address@hidden>
and subject line Re: bug#2827: Can't use Caps Lock on Windows
has caused the Emacs bug report #2827,
regarding Can't use Caps Lock on Windows
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact address@hidden
immediately.)


-- 
2827: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=2827
Emacs Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: Can't use Caps Lock on Windows Date: 30 Mar 2009 23:41:28 -0000
--text follows this line--

Please write in English if possible, because the Emacs maintainers
usually do not have translators to read other languages for them.

Your bug report will be posted to the address@hidden mailing list,
and to the gnu.emacs.bug news group.

Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:

1. Type the characters "lowercase" followed by return.
2. Press Caps Lock
3. Type the characters "uppercase"

None of the characters will be in uppercase. All other Windows
applications deal with Caps Lock correctly.

w32-enable-caps-lock is t

Similar to the issue described in 
<http://groups.google.com/group/gnu.emacs.help/browse_thread/thread/ec345c61bc963d8>
 but no solution was supplied there.

If Emacs crashed, and you have the Emacs process in the gdb debugger,
please include the output from the following gdb commands:
    `bt full' and `xbacktrace'.
If you would like to further debug the crash, please read the file
c:/Program Files/GNU Emacs/etc/DEBUG for instructions.


In GNU Emacs 22.1.1 (i386-mingw-nt5.1.2600)
 of 2007-06-02 on RELEASE
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (3.4) --cflags -Ic:/gnuwin32/include'

Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: en_US
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: en_US.UTF-8
  locale-coding-system: cp1252
  default-enable-multibyte-characters: t

Major mode: Lisp Interaction

Minor modes in effect:
  encoded-kbd-mode: t
  tooltip-mode: t
  tool-bar-mode: t
  mouse-wheel-mode: t
  menu-bar-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  blink-cursor-mode: t
  unify-8859-on-encoding-mode: t
  utf-translate-cjk-mode: t
  auto-compression-mode: t
  line-number-mode: t

Recent input:
l o w e r c a s e <return> u p p e r c a s e M-x r 
e p o r t - e m a c <return>

Recent messages:
("c:\\Program Files\\GNU Emacs\\bin\\emacs.exe" "--no-init-file" 
"--no-site-file")
Loading encoded-kb...done
For information about the GNU Project and its goals, type C-h C-p. [2 times]
Loading emacsbug...
Loading regexp-opt...done
Loading emacsbug...done




--- End Message ---
--- Begin Message --- Subject: Re: bug#2827: Can't use Caps Lock on Windows Date: Thu, 29 Oct 2009 22:47:22 +0800 User-agent: Mozilla-Thunderbird 2.0.0.22 (X11/20090706)
Jason Rumney wrote:
Michael Hoffman wrote:
Since the problem now seems to be fixed, it seems you can mark this bug invalid. Sorry about the inconvenience.

I think it is better to leave it open, tagged as moreinfo, until we understand the cause, so we can document it in etc/PROBLEMS.

Thanks to the observation of Black Qin on the help-gnu-emacs list that this is triggered by scroll lock being on, I have tracked this down to an inapproptiate default value of w32-scroll-lock-modifier. Putting the following in your init file should fix the problem if you cannot update immediately:

(setq w32-scroll-lock-modifier nil)


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]