public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: Multi-term in Emacs under Cygwin doesn't correctly identify terminal type?
Date: Fri, 03 Jun 2011 11:59:00 -0000	[thread overview]
Message-ID: <4DE8CC8D.50600@cornell.edu> (raw)
In-Reply-To: <BANLkTimF_FW2FrVxur++z5hUfFfYLo+MHw@mail.gmail.com>

On 6/2/2011 11:47 PM, Duncan Bayne wrote:
> Hi All,
>
> I've installed Cygwin on Windows 7 Ultimate 64-bit. After a rebaseall,
> Cygwin works nicely. However, I use multi-term in my default Emacs
> setup, and multi-term doesn't seem to like Cygwin at all.
>
> It looks as though multi-term isn't correctly identifying the terminal
> type. It's writing what I think are control characters visibly in the
> buffer, and simple things like clear and linefeeds don't work.
>
> Here's what it looks like at startup:
>
> http://i.stack.imgur.com/RJYDy.jpg
>
> Could someone please suggest a way of getting this working? I'm very
> used to having multiple terminals available in Emacs on Linux,&  would
> hate to lose this functionality under Cygwin.

I don't know anything about multi-term, but the display of control 
characters in the buffer might be caused by your PS1 setting.  See item 
3 under "Usage notes" in /usr/share/doc/Cygwin/emacs.README .

If you write again about this, please follow the problem-reporting 
guidelines at

   http://cygwin.com/problems.html .

Also, please give a precise recipe for reproducing the problem, 
preferably starting with `emacs -Q'.  And say how you are starting emacs 
(under X?  in mintty?).

Ken

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

      parent reply	other threads:[~2011-06-03 11:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-03  3:48 Duncan Bayne
2011-06-03 10:34 ` Marc Girod
2011-06-03 11:59 ` Ken Brown [this message]

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=4DE8CC8D.50600@cornell.edu \
    --to=kbrown@cornell.edu \
    --cc=cygwin@cygwin.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).