From: christos@zoulas.com (Christos Zoulas)
To: Steve Kelem <kelem@adaptivesilicon.com>,
Cygwin <cygwin@sourceware.cygnus.com>
Subject: Re: proper terminal type for tcsh under Cygwin?
Date: Tue, 21 Mar 2000 12:42:00 -0000 [thread overview]
Message-ID: <200003212042.PAA24006@hrothgar.gw.com> (raw)
In-Reply-To: <38D7D813.548A268D@adaptivesilicon.com>
On Mar 21, 12:14pm, kelem@adaptivesilicon.com (Steve Kelem) wrote:
-- Subject: proper terminal type for tcsh under Cygwin?
| This is a multi-part message in MIME format.
| --------------749D8510AAEEA47091297500
| Content-Type: text/plain; charset=us-ascii
| Content-Transfer-Encoding: 7bit
|
| What's the proper terminal type for running tcsh under Cygwin 1.0?
| term=linux doesn't support character insert (type something on the
| command line, then move the cursor to the beginning of the line with
| C-a, then start typing. The text doesn't move over for the new
| characters.) or proper line wrapping (run "ls -l | less". Extra newlines
| are displayed.).
| term=ansi does better than linux, but doesn't handle move cursor to
| beginning of line properly. I have prompt="%S%s%m:kelem:%! ". If I type
| "aC-a" (where C-a is control-a), the cursor properly moves to the
| beginning of the line (the character "a"). Similarly, typing "a bC-a"
| also works. However, typing "a b cC-a" moves the cursor to the space
| before the "a".
Maybe term=vt100 ?
christos
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next prev parent reply other threads:[~2000-03-21 12:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-21 12:14 Steve Kelem
2000-03-21 12:42 ` Christos Zoulas [this message]
2000-03-21 13:34 ` Chris Faylor
2000-03-21 13:53 ` Steve Kelem
2000-03-21 15:32 ` Christos Zoulas
2000-03-21 15:58 ` Chris Faylor
2000-03-21 17:04 ` Steve Kelem
2000-03-21 17:31 ` Chris Faylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200003212042.PAA24006@hrothgar.gw.com \
--to=christos@zoulas.com \
--cc=cygwin@sourceware.cygnus.com \
--cc=kelem@adaptivesilicon.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).