From mint-bounce@lists.fishpool.fi Sun Jul 4 14:21:06 2010 Message-ID: <4C30D0CA.5030504@online.no> Date: Sun, 04 Jul 2010 20:19:54 +0200 From: Jo Even Skarstein User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.9) Gecko/20100423 Thunderbird/3.0.4 MIME-Version: 1.0 To: mint@lists.fishpool.fi Subject: Re: [MiNT] Keyboard-problem with XaAES helmut-branch References: <4C128FBE.7010402@online.no> <4C12AC8D.3050101@online.no> <4C12B776.5030907@online.no> <4C135D23.2050409@online.no> <4C23D3D4.4000006@online.no> <4C2623C6.2010808@online.no> <4C277EAF.8020202@online.no> <4C27A95A.2010909@online.no> <4C27B3DF.3090404@online.no> <4C27C1A3.4070608@online.no> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: joska@online.no Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: On 07/04/2010 09:28 AM, Helmut Karlowski wrote: > I've found the reason: Console is set to COOKED by XaAES during init, > because else > there would be no \n->\r\n-translation in the console-window. You cannot > have both. Why is this translation necessary? On Atari/TOS, cr+lf is the norm anyway. Jo Even