From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-users-return-18544-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 27954 invoked by alias); 2 Mar 2014 18:19:10 -0000
Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Users List <zsh-users.zsh.org>
List-Post: <mailto:zsh-users@zsh.org>
List-Help: <mailto:zsh-users-help@zsh.org>
X-Seq: 18544
Received: (qmail 21739 invoked from network); 2 Mar 2014 18:18:56 -0000
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW
	autolearn=ham version=3.3.2
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type;
        bh=NLTpCysAf72Nv+qIvTUAoEzME8Pj0w3c2q1fvkx/eu4=;
        b=pKh/vZijMphSwCYhUZCPbgb++iCd7I4Vp72Y2R/COi9/FUO5zR0scLuZ5x/xRd5lJO
         yWM9z3WJcUkAtux5LWIi1z4ZgIBQvIrKL2DVwyCiYWaRCPjwyQiVPyGNi4WR5teUhS9D
         s2PL+hdUiiQDzHKi5yg4wWtV76coz/Z/MPlN/f9Ci9QhGcInRI0EpU07UH54xxoxD/FU
         Df2r08uVpW+uc4lBU75FDUmbOhZYIO/aouIZ3f4PHfJ+J7xJHOS7027maGvmF3O1N731
         BUla91B+K/xsMQ5fCZZGMo0IWNFbZQHM91L6qoByyJ69pjySL8UW8MZK7trogqIZ65on
         Eurw==
MIME-Version: 1.0
X-Received: by 10.52.135.65 with SMTP id pq1mr22466661vdb.13.1393784331113;
 Sun, 02 Mar 2014 10:18:51 -0800 (PST)
In-Reply-To: <140302092725.ZM923@torch.brasslantern.com>
References: <CAHyxEs0RWnm_h1X6C6+VognALdCjZDabBATjUUtSUR58x+nHDw@mail.gmail.com>
	<140204073937.ZM21329@torch.brasslantern.com>
	<52F1146D.5020801@eastlink.ca>
	<140204194650.ZM21787@torch.brasslantern.com>
	<52F283E8.4050500@eastlink.ca>
	<CAH+w=7aqdvx52VFv6MCrkUKqt+5tzH665H_X6U1e1SMvNQF1ig@mail.gmail.com>
	<530CB4E8.8050305@eastlink.ca>
	<140225094657.ZM2214@torch.brasslantern.com>
	<530CE01D.9080201@eastlink.ca>
	<140225112152.ZM2295@torch.brasslantern.com>
	<530CF1D5.2050805@eastlink.ca>
	<140226182921.ZM3650@torch.brasslantern.com>
	<530EC7EA.8020602@eastlink.ca>
	<530ECE6B.50605@eastlink.ca>
	<140228210859.ZM5878@torch.brasslantern.com>
	<5312469E.5080907@eastlink.ca>
	<CAH_OBid6uFnVghuKjiKoFEiza0FrHWD0=USV=VVbgA4N+LVbYQ@mail.gmail.com>
	<140302092725.ZM923@torch.brasslantern.com>
Date: Sun, 2 Mar 2014 13:18:51 -0500
Message-ID: <CAH_OBifUcMzyhT+=rqkj4_bo6+97qk+ZjgR6Kp9r27hewqy+zA@mail.gmail.com>
Subject: Re: key codes table.
From: shawn wilson <ag4ve.us@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh Users <zsh-users@zsh.org>
Content-Type: multipart/alternative; boundary=bcaec52d5729f31aef04f3a3b374

--bcaec52d5729f31aef04f3a3b374
Content-Type: text/plain; charset=UTF-8

Hummm, I know this should be possible with qemu but a quick Google is
failing to find an easy way to do this. There's probably a fake serial
device kernel module though... I'm not going to try so hard as to go
through a VM but if this is possible without I'll write something.
On Mar 2, 2014 12:28 PM, "Bart Schaefer" <schaefer@brasslantern.com> wrote:

> On Mar 1,  5:50pm, shawn wilson wrote:
> }
> } If you want that chart, you should be able to come up with a script that
> } gets key bindings for \x00 - \x255 (or more realistically 80~200 -
> } printable characters) and we can run it through common environments?
>
> The problem is getting the keyboard to send those characters.  In an
> XKB environment you might be able to read out the keyboard definitions
> but that won't help for consoles, ssh connections, etc.  It would be
> (was, in the past, IIRC) a large security problem if there were a way
> to script a keyboard to send back arbitrary keystrokes.
>

--bcaec52d5729f31aef04f3a3b374--