From mint-bounce@lists.fishpool.fi  Sat Jul 30 22:34:11 2005
X-Original-To: fnaumann@mail.boerde.de
Delivered-To: fnaumann@mail.boerde.de
Message-ID: <20050730143117.lwtqelc8ry0wccss@coolrunningconcepts.com>
Date: Sat, 30 Jul 2005 14:31:17 -0600
From: evan@coolrunningconcepts.com
To: Andreas Schwab <schwab@suse.de>
Cc: Lonny Pursell <atari@bright.net>,
        "[MiNT] Mailing-List" <mint@fishpool.com>
Subject: Re: [MiNT] GEM edit field question
References: <BF113F14.18EF4%atari@bright.net>
	<jell3ohycm.fsf@sykes.suse.de>
In-Reply-To: <jell3ohycm.fsf@sykes.suse.de>
MIME-Version: 1.0
Content-Type: text/plain;
	charset=ISO-8859-1;
	format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
User-Agent: Internet Messaging Program (IMP) H3 (4.0)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - esc14.midphase.com
X-AntiAbuse: Original Domain - fishpool.com
X-AntiAbuse: Originator/Caller UID/GID - [32001 502] / [47 12]
X-AntiAbuse: Sender Address Domain - coolrunningconcepts.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-ecartis-version: Ecartis v1.0.0
Sender: mint-bounce@lists.fishpool.fi
Errors-To: mint-bounce@lists.fishpool.fi
X-original-sender: evan@coolrunningconcepts.com
Precedence: bulk
List-help: <mailto:ecartis@lists.fishpool.fi?Subject=help>
List-unsubscribe: <mailto:mint-request@lists.fishpool.fi?Subject=unsubscribe>
List-Id: <mint.lists.fishpool.fi>
X-List-ID: <mint.lists.fishpool.fi>
X-Virus-Scanned: by amavisd-new at relay.boerde.de
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on relay.boerde.de
X-Spam-Status: No, hits=-0.3 tagged_above=-50.5 required=7.0 tests=AWL,
 BAYES_00, NO_REAL_NAME
X-Spam-Level: 

Quoting Andreas Schwab <schwab@suse.de>:

> Lonny Pursell <atari@bright.net> writes:
>
>> Is it just a bad design from 1985 when the assumption was the '@' char would
>> probably not be used?  Anyone know?  Documented somewhere?

OK - I don't understand the problem.   How does using the @ sign the 
source code
affect the GEM edit field?   Surely you can type an @ into a GEM edit 
field!  I
don't remember that ever being a problem in the past.   If this is the 
case, we
should change it.

> The original tty kill character in UNIX was @.

No it wasn't.  Its always been the DEL character, which often shows up 
as ^@.  I
even have an AT&T 3B2 machine running SysVr3.1 (the class of machine 
that SysVr4
was written on) and its set to DEL, not @.

If there is some correlation between the AES and STTY settings, then the AES
should follow what the MiNT kernel says are editing characters, thus 
you should
be able to change your edit keys via STTY, or some control panel that uses the
same interface.


