[debbugs-tracker] bug#7637: closed (24.0.50; Caps Lock triggers set-mark-command)

[GNU bug Tracking System]

Your message dated Sat, 15 Oct 2016 17:23:59 +0300
with message-id <address@hidden>
and subject line Re: bug#24456: 25.1; [PATCH] Caps-lock doesn't affect 
interpretation of key chords
has caused the debbugs.gnu.org bug report #24456,
regarding 24.0.50; Caps Lock triggers set-mark-command
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
24456: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=24456
GNU Bug Tracking System
Contact address@hidden with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> 24.0.50; Caps Lock triggers set-mark-command
>
>
>
>
> Date: 
>
> Tue, 14 Dec 2010 12:43:43 +0100
>
>
>
>
> Turning on caps lock also turns on set-mark-command.
> All C- and M- moving commands from then on mark text
> into a region.
> This does not apply for the four arrow keys.
>
> To reproduce:
> 1) Write some text.
>
> 2) Set caps lock to on.
> 3) Move around the text with C-p, C-n, M-b, M-f and other
>    C- and M- keys for moving point.
>
> Region is now marked despite that no C-<SPC> was pressed
> or otherwise set-mark-command invoked.
>
>
> In GNU Emacs 24.0.50.1 (i686-pc-linux-gnu, GTK+ Version 2.12.12)
>  of 2010-12-13 on tiger
> Windowing system distributor `The X.Org Foundation', version 11.0.10402000
> Important settings:
>   value of $LC_ALL: nil
>
>   value of $LC_COLLATE: nil
>   value of $LC_CTYPE: nil
>   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
>   value of $XMODIFIERS: nil
>
>   locale-coding-system: utf-8-unix
>   default enable-multibyte-characters: t
>
> Major mode: Fundamental
>
> Minor modes in effect:
>   tooltip-mode: t
>   mouse-wheel-mode: t
>   tool-bar-mode: t
>   menu-bar-mode: t
>
>   file-name-shadow-mode: t
>   global-font-lock-mode: t
>   blink-cursor-mode: t
>   auto-composition-mode: t
>   auto-encryption-mode: t
>   auto-compression-mode: t
>   line-number-mode: t
>   transient-mark-mode: t
>
> Recent input:
> M-x r e p o r t - e m <tab> <return>
>
> Recent messages:
> For information about GNU Emacs and the GNU system, type C-h C-a.
>
> Features:
> (shadow sort gnus-util mail-extr message sendmail regexp-opt rfc822 mml
>
> easymenu mml-sec mm-decode mm-bodies mm-encode mail-parse rfc2231
> rfc2047 rfc2045 ietf-drums mm-util mail-prsvr mailabbrev mail-utils
> gmm-utils mailheader emacsbug tooltip ediff-hook vc-hooks
> lisp-float-type mwheel x-win x-dnd tool-bar dnd fontset image fringe
>
> lisp-mode register page menu-bar rfn-eshadow timer select scroll-bar
> mouse jit-lock font-lock syntax facemenu font-core frame cham georgian
> utf-8-lang misc-lang vietnamese tibetan thai tai-viet lao korean
> japanese hebrew greek romanian slovak czech european ethiopic indian
>
> cyrillic chinese case-table epa-hook jka-cmpr-hook help simple abbrev
> loaddefs button minibuffer faces cus-face files text-properties overlay
> md5 base64 format env code-pages mule custom widget
> hashtable-print-readable backquote make-network-process dbusbind
>
> dynamic-setting system-font-setting font-render-setting move-toolbar gtk
> x-toolkit x multi-tty emacs)
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#24456: 25.1; [PATCH] Caps-lock doesn't affect interpretation of key chords
>
>
>
>
> Date: 
>
> Sat, 15 Oct 2016 17:23:59 +0300
>
>
>
>
> > Date: Sat, 01 Oct 2016 18:59:05 +0300
> > From: Eli Zaretskii <address@hidden>
> > Cc: address@hidden, address@hidden
> > 
> > > From: Dima Kogan <address@hidden>
> > > Cc: address@hidden, address@hidden
> > > Date: Sat, 01 Oct 2016 08:12:27 -0700
> > > 
> > > > Looks okay, but you still didn't leave a space before the opening
> > > > parentheses and the function name.
> > > 
> > > Attached.
> > 
> > Looks good, thanks.
> > 
> > > Is there a tool to automatically detect/fix these?
> > 
> > I'm not aware of any, but that doesn't mean there isn't one.
> > 
> > > > Did you try this with a non-ASCII key (assuming you have one on your
> > > > keyboard)?
> > > 
> > > I did not try. I live in the US, and pretty much never see keyboards
> > > with anything non-trivial on them. If somebody else would test it, that
> > > would be great.
> > 
> > Could someone please try that and see if it works correctly?
>
> No further comments, so I pushed this to the master branch, and I'm
> marking this bug done.
>
> Thanks.
>
>
> --- End Message ---