From owner-freebsd-questions  Thu Nov 30 10:47:18 1995
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id KAA10264
          for questions-outgoing; Thu, 30 Nov 1995 10:47:18 -0800
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id KAA10255
          for <freebsd-questions@freefall.freebsd.org>; Thu, 30 Nov 1995 10:47:15 -0800
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA01109; Thu, 30 Nov 1995 11:35:45 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199511301835.LAA01109@phaeton.artisoft.com>
Subject: Re: ^Z behaviour
To: kuku@gilberto.physik.rwth-aachen.de (Christoph P. Kukulies)
Date: Thu, 30 Nov 1995 11:35:44 -0700 (MST)
Cc: freebsd-questions@freefall.freebsd.org
In-Reply-To: <199511301131.MAA24728@gilberto.physik.rwth-aachen.de> from "Christoph P. Kukulies" at Nov 30, 95 12:31:49 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 1077      
Sender: owner-questions@FreeBSD.ORG
Precedence: bulk

> I got a phone call from a (otherwise happy) FreeBSD customer
> who is using FreeBSD 2.0.5 in an industrial production environment
> (btw) and he is 'complaining' about the ^Z behaviour.
> 
> His users were happy users of the med editor (ex PCS people, 
> when will be a port of med available? Jordan, are you listening ?:-)
> and have this ^Z built into their finger memory. So it happens
> that they send vi permanently into background, wondering and starting
> over with a pile of vi sessions in bg.
> 
> I tried stty susp ^P or something but it seems that the ^Z
> behaviour is built into vi.
> 
> Any ideas how to help these people?

Set the global EXINIT or put in the user's .exrc:

map ^Z q
    ^
    |
    real "control-z"

Use of ^Z in insert mode will insert ^Z.
Use of ^Z in command mode will give the error "q isn't a vi command."

Obviously, vi should respect the tty modes, so the real fix is to
send the bug in to Keith.


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.