Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com From: Chris Faylor Date: Tue, 21 Mar 2000 18:58:35 -0500 To: cygwin AT sourceware DOT cygnus DOT com Subject: Re: proper terminal type for tcsh under Cygwin? Message-ID: <20000321185835.A21861@cygnus.com> Reply-To: cygwin AT sourceware DOT cygnus DOT com Mail-Followup-To: cgf AT cygnus DOT com, cygwin AT sourceware DOT cygnus DOT com References: <38D7EF29 DOT F0C86D4C AT adaptivesilicon DOT com> <200003212332 DOT SAA03676 AT hrothgar DOT gw DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.8i In-Reply-To: <200003212332.SAA03676@hrothgar.gw.com>; from christos@zoulas.com on Tue, Mar 21, 2000 at 06:32:35PM -0500 On Tue, Mar 21, 2000 at 06:32:35PM -0500, Christos Zoulas wrote: >On Mar 21, 1:52pm, kelem AT adaptivesilicon DOT com (Steve Kelem) wrote: >>set term=cygwin yields no insert mode when you move the cursor into the >>middle of a word. The new characters overwrite the old characters, but >>a C-r shows that the new characters really were inserted. > >I know this is suboptimal, but you can use telltc to figure out what >the bad entries, and settc to fix them. The editor in tcsh will work >properly with most termcap entries empty, but it will be less >efficient. > >When you come up with a working version you can store it in a file or >put it in your TERMCAP environment variable. FWIW, I don't see this problem at all. Inserting a character works correctly for me. You should not have to set the terminal type. It should be automatic. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com