Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!apple!usc!zaphod.mps.ohio-state.edu!ub!uhura.cc.rochester.edu!rochester!pt.cs.cmu.edu!zardoz.club.cc.cmu.edu!ddj
From: ddj@zardoz.club.cc.cmu.edu (Doug DeJulio)
Newsgroups: comp.sys.next
Subject: Re: emacs shell
Keywords: emacs,termcap
Message-ID: <11903@pt.cs.cmu.edu>
Date: 12 Feb 91 04:22:17 GMT
References: <2341@mas1.UUCP>
Organization: Castle Anthrax, Pittsburgh
Lines: 18

In article <2341@mas1.UUCP> wenshenk@mas1.UUCP (Wen-Shen Kao) writes:
>        I have a minor problem with the emacs editor, maybe someone can give
>me some advices. When I spawn a shell within emacs editor by issuing "shell" 
>command, the emacs prompts "incomplete termcap entry, editing disabled".

Ignore this, it's not a problem.  It won't hurt emacs at all.  The
NeXT machine doesn't have an ordinary CSH, it has CMU's modified CSH
with command line editing and other nifty features.  In order for
those features to work, csh needs to know what terminal type you have.
The csh that's running *under* *emacs* isn't running in a VT100 or
under any other sort of terminal emulator -- emacs provides a dumb
terminal environment for it.  Because of this, the csh is notifying
you that you can't use features like command line editing -- which you
don't need because the shell is in an emacs buffer anyway.
-- 
Doug DeJulio
ddj@zardoz.club.cc.cmu.edu (NeXT)
dd26+@andrew.cmu.edu (AMS/ATK)