From mint-bounce@lists.fishpool.fi Fri Jul 24 04:57:31 2009 From: Andreas Schwab To: "Helmut Karlowski" Cc: mint@lists.fishpool.fi Subject: Re: [MiNT] code for Ctrl-6,Ctrl-2 References: X-Yow: .. Once upon a time, four AMPHIBIOUS HOG CALLERS attacked a family of DEFENSELESS, SENSITIVE COIN COLLECTORS and brought DOWN their PROPERTY VALUES!! Date: Fri, 24 Jul 2009 10:54:20 +0200 In-Reply-To: (Helmut Karlowski's message of "Thu, 23 Jul 2009 22:56:37 +0200") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.96 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Scanned-By: MIMEDefang 2.58 on 172.16.27.26 X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: schwab@linux-m68k.org Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: "Helmut Karlowski" 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- 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."