Your message dated Sat, 14 Oct 2017 11:25:36 -0400
with message-id <[email protected]>
and subject line Re: Bug#839770: keysym syntax can't handle M-C-s
has caused the Debian Bug report #839770,
regarding keysym syntax can't handle M-C-s
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 [email protected]
immediately.)
--
839770: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839770
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: rxvt-unicode
Version: 9.22-1+b1
Severity: minor
Tags: upstream
I used to have
URxvt.searchable-scrollback: CM-s
and wanted to replace that with the "new" syntax:
URxvt.keysym.MC-s: searchable-scrollback:start
While the former works as expected, the latter does not properly.
Specifically, MC-s does work, but so does M-s by itself. This is of
course highly annoying and also not designed behaviour according to
the manpage:
"a key mapping will match if at least the specified identifiers
are being set, and no other key mappings with those and more bits
are being defined."
This means that CM-NumLock-Shift-s will trigger the same as CM-s,
unless that is actually defined.
However, in my case, M-S does not fulfill "at least the specified
identifiers", as Control is missing.
The workaround seems to be to add
URxvt.keysym.M-s: builtin:
Note that this is not required in other cases, e.g. CM-Return works
fine (M-Return is not modified).
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages rxvt-unicode depends on:
ii base-passwd 3.5.40
ii libc6 2.24-3
ii libfontconfig1 2.11.0-6.7
ii libfreetype6 2.6.3-3+b1
ii libgcc1 1:6.2.0-4
ii libgdk-pixbuf2.0-0 2.36.0-1
ii libglib2.0-0 2.50.0-1
ii libperl5.24 5.24.1~rc3-3
ii libstartup-notification0 0.12-4
ii libx11-6 2:1.6.3-1
ii libxft2 2.3.2-1
ii libxrender1 1:0.9.9-2
ii ncurses-base 6.0+20160917-1
Versions of packages rxvt-unicode recommends:
ii fonts-dejavu 2.37-1
ii fonts-ipaexfont-gothic [fonts-japanese-gothic] 00301-2
ii fonts-ipafont-gothic [fonts-japanese-gothic] 00303-16
rxvt-unicode suggests no packages.
-- no debconf information
--
.''`. martin f. krafft <[email protected]> @martinkrafft
: :' : proud Debian developer
`. `'` http://people.debian.org/~madduck
`- Debian - when you have better things to do than fixing systems
digital_signature_gpg.asc
Description: Digital GPG signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
--- End Message ---
--- Begin Message ---
Hi Martin,
I discussed this with upstream, and the following change[0] updated
their documentation to appropriately document the mechanisms at hand.
The workaround you found seems to be exactly what was required.
Seeing that this was not a bug, I'm closing it.
Best wishes,
Ryan
[0]
https://github.com/exg/rxvt-unicode/commit/7ad2fa68bdeb30483d957f05d056692c51ed7c3a#diff-89c15a080ed91390105cda3b1c548d3c
--
|_)|_/ Ryan Kavanagh | GPG: 4E46 9519 ED67 7734 268F
| \| \ https://ryanak.ca/ | BD95 8F7B F8FC 4A11 C97A
signature.asc
Description: PGP signature
--- End Message ---
