From owner-freebsd-questions  Fri Apr  7  7:28:29 2000
Delivered-To: freebsd-questions@freebsd.org
Received: from ptavv.es.net (ptavv.es.net [198.128.4.29])
	by hub.freebsd.org (Postfix) with ESMTP id 9916937BC8C
	for <freebsd-questions@FreeBSD.ORG>; Fri,  7 Apr 2000 07:28:26 -0700 (PDT)
	(envelope-from oberman@es.net)
Received: from es.net (localhost [127.0.0.1])
	by ptavv.es.net (8.9.3/8.8.8) with ESMTP id HAA26205;
	Fri, 7 Apr 2000 07:28:20 -0700 (PDT)
Message-Id: <200004071428.HAA26205@ptavv.es.net>
To: William Freeman <wdf@picusnet.com>
Cc: freebsd-questions@FreeBSD.ORG
Subject: Re: backspace key in Vi(m) under Xterm 
In-reply-to: Your message of "Wed, 05 Apr 2000 16:59:51 EDT."
             <38EBA947.3E2F09C0@picusnet.com> 
Date: Fri, 07 Apr 2000 07:28:20 -0700
From: "Kevin Oberman" <oberman@es.net>
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

William,

I would not give up on Emacs so quickly. 

I run XEmacs and fire it up when I log in with no visible frames. I
have the .emacs file launch gnuserv and then use gnuclient as my
editor. It typically brings up a frame with the file I want to edit in
under a second. XEmacs even comes with a shell script to make the edit
command use gnuclient if you have a gnuserv running and xemacs if not,
but I'd prefer to just have XEmacs running at boot time.

I think emacs has similar capability, but I much prefer XEmacs, so I
have not tried it. If you can't make emacs work, try XEmacs. But don't
give up on as excellent an editor as emacs because of a problem so
easily worked around.

R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman@es.net			Phone: +1 510 486-8634


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message