linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michel Lanners <mlan@cpu.lu>
To: costabel@wanadoo.fr
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Keyboard trouble with XF 4.0.1
Date: Sun, 29 Oct 2000 17:47:10 +0100 (CET)	[thread overview]
Message-ID: <200010291647.RAA01482@piglet.grunz.lu> (raw)
In-Reply-To: <39F33A92.751C5F@wanadoo.fr>


Hi all,

On  22 Oct, this message from Martin Costabel echoed through cyberspace:
> I can tell you what is working for me. I have been using Franz's XF4
> RPMs for quite a while without major problems (some minor ones still
> persist, but since the RPMs are 3 months old, I won't repeat them here).
> I am not using, however, the "linux" keycodes. Only the ADB codes.

I went back now to ADB kezcodes as well, since MOL doesn't seem to work
with Linux keycodes.

> I am using the same keymaps as I have for years with the "old" input
> layer.

And which ones are those? Where did you get them from?

> The only problem are those 2 swapped keys "@#" vs "<>".

For the record, with ADB keycodes, all keys are OK in MOL _except_ those
two swapped keys. I wonder whether swapping them is such a good idea...

> In keycodes/macintosh, besides the usual definition of keycode 18, the
                                                         ^^^^^^^^^^
Which one is this?

> Otherwise, in keymap/macintosh:
>
> -    xkb_symbols                { include "macintosh/us(extended)" };
> +    xkb_symbols                { include "macintosh/fr" };

I have no macintosh/fr file. Where did you get yours from?

> In XF86Config, I have
>
> #    Option "XkbDisable"
>     Option "XkbRules"   "xfree86"
>     Option "XkbModel"   "macintosh_old"
>     Option "XkbLayout"  "fr"
>     Option "XkbCompat"  ""

I still don't see how those Xkb options relate to anything in the files
below /usr/lib/X11/xkb. Anybody can explain this?

Thanks

Michel

-------------------------------------------------------------------------
Michel Lanners                 |  " Read Philosophy.  Study Art.
23, Rue Paul Henkes            |    Ask Questions.  Make Mistakes.
L-1710 Luxembourg              |
email   mlan@cpu.lu            |
http://www.cpu.lu/~mlan        |                     Learn Always. "


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2000-10-29 16:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-22 16:30 Keyboard trouble with XF 4.0.1 Michel Lanners
2000-10-22 18:45 ` Benjamin Herrenschmidt
2000-10-22 19:05 ` Martin Costabel
2000-10-22 20:53   ` Benjamin Herrenschmidt
2000-10-22 22:13     ` Martin Costabel
2000-10-23 12:32       ` Benjamin Herrenschmidt
2000-10-29 16:47   ` Michel Lanners [this message]
2000-10-29 18:57     ` Martin Costabel
2000-10-29 22:04       ` Michel Lanners
2000-10-29 21:40     ` Guillaume Laures
2000-10-29 21:59       ` Michel Lanners
2000-10-30  9:43         ` Guillaume Laures
2000-11-02  7:12   ` Michel Lanners
2000-10-29 22:09 ` Michel Lanners
2000-10-30 21:22   ` Keyboard trouble with XF 4.0.1R Guillaume Laures

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200010291647.RAA01482@piglet.grunz.lu \
    --to=mlan@cpu.lu \
    --cc=costabel@wanadoo.fr \
    --cc=linuxppc-dev@lists.linuxppc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).