Bug#165134: acknowledged by developer (Re: Bug#165134: xlibs: [xkb] symbol change in us keyboard disables Meta and Compose key)
severity 165134 wishlist retitle 165134 xlibs: [xkb] please break compatibility with upstream in pc104 symbols file tag 165134 + wontfix thanks > So in Debian 3.0 Windows keys work as Meta keys. Debian 3.x Windows do > not. Yup, no breakage there. People also complained that it was "broken" when the Alt and Meta keys weren't handled the same way on pc101/102 versus pc104/105 keyboards. Both groups can't be right. > What is worse I was using debconf to perform configuration file > handling, this kind of change could have been handled transparently by > having pc104 switch to altwin on upgrade. Well, no. "pc104" is an XkbModel, defined by a subsection of the "us" symbols file. "altwin" in a partial symbols file that will only work as desired as an XkbOptions setting. The Debconf templates have no prior knowledge as to whether the Alt modifiers should be on the same keys as the Meta keysyms[1]. I therefore cannot take your advice without making *someone* unhappy. For the sake of compatiblity with upstream, and people who might choose to migrate their XF86Config files among Linux distributions, I choose to make those who feel as you do unhappy. > As I mentioned you should probably forward this as something for the > Debian 3.x release notes. It is the difference between a Changelog file > and a NEWS file. That is not the nature of your report. Your report tells me I've "broken" it. If you want some documentation, file a wishlist or minor bug, preferably with a patch. Note that I am not the Release Notes Maintainer, so a bug about release notes should not be filed against my package. > > Closing this spurious report. > > Reopened. I guess I'll make both Ian Jackson and Manoj unhappy (have you been reading -project) by both leaving the bug open and tagging it "wontfix". [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=77039&repeatmerged=yes (Which, incidentally, I should be closing. Thanks for the reminder.) [2] If you don't understand all of the above jargon, then you probably don't have sufficient knowledge to responsibly discuss the issue, should defer to those who do, and should close your report. -- G. Branden Robinson| Debian GNU/Linux | kernel panic -- causal failure [EMAIL PROTECTED] | universe will now reboot http://people.debian.org/~branden/ | pgpwYrVGjBlxa.pgp Description: PGP signature
Processed: Re: Bug#165134: acknowledged by developer (Re: Bug#165134: xlibs: [xkb] symbol change in us keyboard disables Meta and Compose key)
Processing commands for [EMAIL PROTECTED]: > severity 165134 wishlist Bug#165134: xlibs: [xkb] symbol change in us keyboard disables Meta and Compose key Severity set to `wishlist'. > retitle 165134 xlibs: [xkb] please break compatibility with upstream in pc104 > symbols file Bug#165134: xlibs: [xkb] symbol change in us keyboard disables Meta and Compose key Changed Bug title. > tag 165134 + wontfix Bug#165134: xlibs: [xkb] please break compatibility with upstream in pc104 symbols file Tags added: wontfix > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#165134: acknowledged by developer (Re: Bug#165134: xlibs: [xkb] symbol change in us keyboard disables Meta and Compose key)
severity 165134 wishlist retitle 165134 xlibs: [xkb] please break compatibility with upstream in pc104 symbols file tag 165134 + wontfix thanks > So in Debian 3.0 Windows keys work as Meta keys. Debian 3.x Windows do > not. Yup, no breakage there. People also complained that it was "broken" when the Alt and Meta keys weren't handled the same way on pc101/102 versus pc104/105 keyboards. Both groups can't be right. > What is worse I was using debconf to perform configuration file > handling, this kind of change could have been handled transparently by > having pc104 switch to altwin on upgrade. Well, no. "pc104" is an XkbModel, defined by a subsection of the "us" symbols file. "altwin" in a partial symbols file that will only work as desired as an XkbOptions setting. The Debconf templates have no prior knowledge as to whether the Alt modifiers should be on the same keys as the Meta keysyms[1]. I therefore cannot take your advice without making *someone* unhappy. For the sake of compatiblity with upstream, and people who might choose to migrate their XF86Config files among Linux distributions, I choose to make those who feel as you do unhappy. > As I mentioned you should probably forward this as something for the > Debian 3.x release notes. It is the difference between a Changelog file > and a NEWS file. That is not the nature of your report. Your report tells me I've "broken" it. If you want some documentation, file a wishlist or minor bug, preferably with a patch. Note that I am not the Release Notes Maintainer, so a bug about release notes should not be filed against my package. > > Closing this spurious report. > > Reopened. I guess I'll make both Ian Jackson and Manoj unhappy (have you been reading -project) by both leaving the bug open and tagging it "wontfix". [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=77039&repeatmerged=yes (Which, incidentally, I should be closing. Thanks for the reminder.) [2] If you don't understand all of the above jargon, then you probably don't have sufficient knowledge to responsibly discuss the issue, should defer to those who do, and should close your report. -- G. Branden Robinson| Debian GNU/Linux | kernel panic -- causal failure [EMAIL PROTECTED] | universe will now reboot http://people.debian.org/~branden/ | msg04382/pgp0.pgp Description: PGP signature
Processed: Re: Bug#165134: acknowledged by developer (Re: Bug#165134: xlibs: [xkb] symbol change in us keyboard disables Meta and Compose key)
Processing commands for [EMAIL PROTECTED]: > severity 165134 wishlist Bug#165134: xlibs: [xkb] symbol change in us keyboard disables Meta and Compose key Severity set to `wishlist'. > retitle 165134 xlibs: [xkb] please break compatibility with upstream in pc104 >symbols file Bug#165134: xlibs: [xkb] symbol change in us keyboard disables Meta and Compose key Changed Bug title. > tag 165134 + wontfix Bug#165134: xlibs: [xkb] please break compatibility with upstream in pc104 symbols file Tags added: wontfix > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#165134 acknowledged by developer (Re: Bug#165134: xlibs: [xkb] symbol change in us keyboard disables Meta and Compose key)
Processing commands for [EMAIL PROTECTED]: > reopen 165134 Bug#165134: xlibs: [xkb] symbol change in us keyboard disables Meta and Compose key Bug reopened, originator not changed. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#165134: acknowledged by developer (Re: Bug#165134: xlibs: [xkb] symbol change in us keyboard disables Meta and Compose key)
reopen 165134 thanks > On Thu, Oct 17, 2002 at 02:41:11PM +1000, Anand Kumria wrote: > > The Windows keys on upgrade don't send Meta anymore. Personally I prefer > > the definition supplied with Debian 3.0 (Left Windows is Meta, Right > > Windows is Compose). > >=20 > > This breaks upgrades (and if it isn't going to be changed should be > > noted on future release notes) and seem somewhat gratuitous. > > Oh, please. It doesn't "break upgrades". No package fails to unpack or > configure due to this. So in Debian 3.0 Windows keys work as Meta keys. Debian 3.x Windows do not. Yup, no breakage there. What is worse I was using debconf to perform configuration file handling, this kind of change could have been handled transparently by having pc104 switch to altwin on upgrade. > It is documented both in the Debian changelog and in the upstream > changelog. As I mentioned you should probably forward this as something for the Debian 3.x release notes. It is the difference between a Changelog file and a NEWS file. > Closing this spurious report. Reopened. Anand -- `` We are shaped by our thoughts, we become what we think. When the mind is pure, joy follows like a shadow that never leaves. '' -- Buddha, The Dhammapada
Bug#165134: acknowledged by developer (Re: Bug#165134: xlibs: [xkb] symbol change in us keyboard disables Meta and Compose key)
reopen 165134 thanks > On Thu, Oct 17, 2002 at 02:41:11PM +1000, Anand Kumria wrote: > > The Windows keys on upgrade don't send Meta anymore. Personally I prefer > > the definition supplied with Debian 3.0 (Left Windows is Meta, Right > > Windows is Compose). > >=20 > > This breaks upgrades (and if it isn't going to be changed should be > > noted on future release notes) and seem somewhat gratuitous. > > Oh, please. It doesn't "break upgrades". No package fails to unpack or > configure due to this. So in Debian 3.0 Windows keys work as Meta keys. Debian 3.x Windows do not. Yup, no breakage there. What is worse I was using debconf to perform configuration file handling, this kind of change could have been handled transparently by having pc104 switch to altwin on upgrade. > It is documented both in the Debian changelog and in the upstream > changelog. As I mentioned you should probably forward this as something for the Debian 3.x release notes. It is the difference between a Changelog file and a NEWS file. > Closing this spurious report. Reopened. Anand -- `` We are shaped by our thoughts, we become what we think. When the mind is pure, joy follows like a shadow that never leaves. '' -- Buddha, The Dhammapada -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#165134 acknowledged by developer (Re: Bug#165134: xlibs: [xkb] symbol change in us keyboard disables Meta and Compose key)
Processing commands for [EMAIL PROTECTED]: > reopen 165134 Bug#165134: xlibs: [xkb] symbol change in us keyboard disables Meta and Compose key Bug reopened, originator not changed. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#165134: xlibs: [xkb] symbol change in us keyboard disables Meta and Compose key
Package: xlibs
Version: 4.2.1-2
Severity: normal
xlibs version 4.1.0-16 (Debian 3.0) contains:
// definition for the extra keys on 104-key "Windows95" keyboards
xkb_symbols "pc104" {
include "us(generic101)"
key {[ Alt_L ] };
key {[ Alt_R ] };
key {[ Meta_L ] };
key {[ Multi_key ] };
key {[ Menu] };
// modifier mappings
modifier_map Mod1 { Alt_L, Alt_R };
modifier_map Mod4 { Meta_L, Meta_R };
};
whereas thone supplied in this version is:
xkb_symbols "pc104" {
include "us(generic101)"
key {[ Alt_L, Meta_L ] };
key {[ Alt_R, Meta_R ] };
key {[ Super_L ] };
key {[ Super_R ] };
key {[ Menu] };
// modifier mappings
modifier_map Mod1 { Alt_L, Alt_R, Meta_L, Meta_R };
modifier_map Mod4 { Super_L, Super_R };
};
The Windows keys on upgrade don't send Meta anymore. Personally I prefer
the definition supplied with Debian 3.0 (Left Windows is Meta, Right
Windows is Compose).
This breaks upgrades (and if it isn't going to be changed should be
noted on future release notes) and seem somewhat gratuitous. What is the
Super key and why do I need one?
Anand
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux clam 2.4.17 #13 Mon Mar 18 12:31:14 EST 2002 i686
Locale: LANG=C, LC_CTYPE=
Versions of packages xlibs depends on:
ii libc6 2.2.5-15 GNU C Library: Shared libraries an
ii libfreetype6 2.1.2-8FreeType 2 font engine, shared lib
ii xfree86-common4.2.1-2X Window System (XFree86) infrastr
-- no debconf information
Bug#165134: xlibs: [xkb] symbol change in us keyboard disables Meta and Compose key
Package: xlibs
Version: 4.2.1-2
Severity: normal
xlibs version 4.1.0-16 (Debian 3.0) contains:
// definition for the extra keys on 104-key "Windows95" keyboards
xkb_symbols "pc104" {
include "us(generic101)"
key {[ Alt_L ] };
key {[ Alt_R ] };
key {[ Meta_L ] };
key {[ Multi_key ] };
key {[ Menu] };
// modifier mappings
modifier_map Mod1 { Alt_L, Alt_R };
modifier_map Mod4 { Meta_L, Meta_R };
};
whereas thone supplied in this version is:
xkb_symbols "pc104" {
include "us(generic101)"
key {[ Alt_L, Meta_L ] };
key {[ Alt_R, Meta_R ] };
key {[ Super_L ] };
key {[ Super_R ] };
key {[ Menu] };
// modifier mappings
modifier_map Mod1 { Alt_L, Alt_R, Meta_L, Meta_R };
modifier_map Mod4 { Super_L, Super_R };
};
The Windows keys on upgrade don't send Meta anymore. Personally I prefer
the definition supplied with Debian 3.0 (Left Windows is Meta, Right
Windows is Compose).
This breaks upgrades (and if it isn't going to be changed should be
noted on future release notes) and seem somewhat gratuitous. What is the
Super key and why do I need one?
Anand
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux clam 2.4.17 #13 Mon Mar 18 12:31:14 EST 2002 i686
Locale: LANG=C, LC_CTYPE=
Versions of packages xlibs depends on:
ii libc6 2.2.5-15 GNU C Library: Shared libraries an
ii libfreetype6 2.1.2-8FreeType 2 font engine, shared lib
ii xfree86-common4.2.1-2X Window System (XFree86) infrastr
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
