linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mattia Dongili <dongili@supereva.it>
To: junkio@cox.net
Cc: Norman Diamond <ndiamond@wta.att.ne.jp>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] keycode 183 in defkeymap.map (was Re: Japanese keyboards broken in 2.6)
Date: Thu, 24 Jul 2003 14:39:08 +0200	[thread overview]
Message-ID: <20030724123908.GA637@inferi.kami.home> (raw)
In-Reply-To: <7vznj4ua3e.fsf_-_@assigned-by-dhcp.cox.net>

On Wed, Jul 23, 2003 at 03:55:33PM -0700, junkio@cox.net wrote:
> >>>>> "ND" == Norman Diamond <ndiamond@wta.att.ne.jp> writes:
> 
> ND> "Andries Brouwer" <aebr@win.tue.nl> replied to me, thank you.  Again, sorry
> ND> I cannot keep up with the mailing list.  If Dr. Brouwer or anyone else has
> ND> advice or questions, please contact me directly.  I am sending this both
> ND> personally and to the list.
> 
> I also got help from Brouwer with a similar (maybe the same)
> problem.  Although his "keycode 183 = backslash bar" comment is
> a bit cryptic, but here is what I did and worked:
[...] 
> For your convenience, I have attached patch that updates
> defkeymap.c and defkeymap.map to include the key definition, so
> you do not have to recompile loadkeys just to regenerate
> defkeymap.c file.  You should be able to apply the following to
> your 2.6.0-test1 source and rebuild the kernel.

thanks, it works as expected, my pipe key is back!
-- 
mattia
:wq!

      reply	other threads:[~2003-07-24 12:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.i32jisu.1s68kri@ifi.uio.no>
     [not found] ` <fa.i0hls5p.1rneqjr@ifi.uio.no>
2003-07-23 22:55   ` [PATCH] keycode 183 in defkeymap.map (was Re: Japanese keyboards broken in 2.6) junkio
2003-07-24 12:39     ` Mattia Dongili [this message]

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=20030724123908.GA637@inferi.kami.home \
    --to=dongili@supereva.it \
    --cc=junkio@cox.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ndiamond@wta.att.ne.jp \
    /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).