On Sun, Sep 19, 2004 at 02:28:17PM +0200, Denis Barbier wrote:
> On Sun, Sep 19, 2004 at 10:35:08AM +0200, Denis Barbier wrote:
> [...]
> > The problem is that changes were made upstream in xlibs to improve support
> > for multiple layouts. Some applications are confused and fail to handle
> > the current keymaps.
> > So there are 2 solutions:
> > a. Fix xlibs.
> > b. Fix those applications.
> [...]
>
> I should have mentioned that there is a 3rd way, which is to add an
> option to disable fake keys. It will revert fixes applied against
> pristine 4.3.0 and bugs will surface again when this option is
> activated. I believe that this option should be added for sarge,
> but users have to be warned that it is unuspported, ie. if this
> option causes trouble to some users, their only choice is to
> deactivate it.
> It can be defined by:
> partial function_keys
> xkb_symbols "no_fake_keys" {
> modifier_map none { <META>, <SUPR>, <HYPR> };
> };
> and rules/xfree.{lst,xml} must be updated too.
> XSF guys, what do you think about it?
Denis,
I'm sorry it has taken me a while to get back to this.
I say: Go for it. Once this is done, I think we'll want to update the
debconf template for XkbOptions and maybe NEWS.Debian as well; there are a
lot of Emacs and Sawfish users out there.
--
G. Branden Robinson |
Debian GNU/Linux | If existence exists,
branden@debian.org | why create a creator?
http://people.debian.org/~branden/ |
Attachment:
signature.asc
Description: Digital signature