[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MiNT] code for Ctrl-6,Ctrl-2

To: "Helmut Karlowski" <helmut.karlowski@ish.de>
Subject: Re: [MiNT] code for Ctrl-6,Ctrl-2
From: Andreas Schwab <schwab@linux-m68k.org>
Date: Fri, 24 Jul 2009 10:54:20 +0200
Cc: mint@lists.fishpool.fi
In-reply-to: <op.uxjggnztofd6j1@descaro> (Helmut Karlowski's message of "Thu, 23 Jul 2009 22:56:37 +0200")
List-help: <mailto:ecartis@lists.fishpool.fi?Subject=help>
List-id: <mint.lists.fishpool.fi>
List-owner: <mailto:tjhukkan@fishpool.fi>
List-post: <mailto:mint@lists.fishpool.fi>
List-subscribe: <mailto:mint-request@lists.fishpool.fi?Subject=subscribe>
List-unsubscribe: <mailto:mint-request@lists.fishpool.fi?Subject=unsubscribe>
References: <op.uxjggnztofd6j1@descaro>
Sender: mint-bounce@lists.fishpool.fi
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.96 (gnu/linux)

"Helmut Karlowski" <helmut.karlowski@ish.de> writes:

> as we are talking about keyboard-input: I just discovered an odd
> behaviour: TOS returns 0x14 on Ctrl-4, 0x15 on Ctrl-5, and 0x1e on
> Ctrl-6.  Ctrl-7 is 0x17 in the low byte. So Ctrl-6 is not logically
> set. The new  MiNT returns 0x16, as one should expect. In scancode.h
> (by purec) 0x1e is  given.
>
> Same for Ctrl-2: 0x02 new, 0x00 old.
>
> Where those codes intentionally given? 0x16 == ^V?

AFAIK the Ctrl-<N> codes generated by TOS are compatible with the VT52
terminal.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

References:
- [MiNT] code for Ctrl-6,Ctrl-2
  - From: "Helmut Karlowski" <helmut.karlowski@ish.de>

Prev by Date: Re: [MiNT] XaAES
Next by Date: Re: [MiNT] Highwire edit
Previous by thread: [MiNT] code for Ctrl-6,Ctrl-2
Next by thread: [MiNT] Native gcc 4.4.1 and binutils 2.19.1
Index(es):
- Date
- Thread