Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!usc!wuarchive!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!midway!mimsy!haven!wam!cville.umd.edu!charlie
From: charlie@cville.umd.edu (Charles William Fletcher)
Newsgroups: comp.sys.next
Subject: Re: emacs shell
Keywords: emacs,termcap
Message-ID: <1991Feb12.171409.26666@wam.umd.edu>
Date: 12 Feb 91 17:14:09 GMT
References: <2341@mas1.UUCP> <11903@pt.cs.cmu.edu>
Sender: usenet@wam.umd.edu (USENET Posting)
Organization: University of Maryland at College Park
Lines: 35

In article <11903@pt.cs.cmu.edu> ddj@zardoz.club.cc.cmu.edu (Doug DeJulio) writes:
>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)


This brings in another related problem. Say you spawn the shell
(and get the termcap problem); and (say) you compile a TeX file
with an error. By typing an 'e' at this point (and assuming the
proper shell set up), you are then inserted into emacs at the line
where the error occured. Under the emacs shell, this won't work due to 
he improper termcap file. In reality, I don't want it to work, since
it would mean having a *new* emacs spawn and cause the file to be
edited in two separate processes. *What I would like* is to be placed
back in the *existing* emacs buffer at the correct line (where the
error exists.) Is this possible? Any emacs gurus out there or should I
post this to comp.sys.emacs?? I assume the same type of behavior occurs
when compiling C code, but I haven't done that yet.

Thanks,