public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Chris Green <chris@areti.co.uk>
To: cygwin-xfree@cygwin.com
Subject: Re: rxvt comes up with lots of escape sequences visible
Date: Sat, 03 Jan 2004 19:19:00 -0000 [thread overview]
Message-ID: <20040103191921.GB8247@areti.co.uk> (raw)
In-Reply-To: <20040103190038.GA3825@redhat.com>
On Sat, Jan 03, 2004 at 02:00:38PM -0500, Christopher Faylor wrote:
> On Sat, Jan 03, 2004 at 06:18:37PM +0000, Chris Green wrote:
> >On Sat, Jan 03, 2004 at 12:55:05PM -0500, Igor Pechtchanski wrote:
> >> On Sat, 3 Jan 2004, Chris Green wrote:
> >>
> >> > When I start an rxvt window on my cygwin X display (a local win2k rxvt
> >> > client that is) it has lots of visible escape sequences, e.g.:-
> >> >
> >> > \[\033]0;\w\007
> >> > \033[32m\]\u@\h \[\033[33m\w\033[0m\]
> >> >
> >> > Presumably these should be interpreted somehow by rxvt and not
> >> > displayed. What am I doing wrong?
> >> >
> >> > The window works otherwise, it redisplays the above after every
> >> > command though.
> >> >
> >> > I've not done anything apart from installing rxvt (by using
> >> > startup.exe) and then running rxvt.
> >>
> >> It's the default *bash* prompt as displayed by ash. For some reason, rxvt
> >> doesn't pick up that your shell is bash and invokes /bin/sh, which doesn't
> >> understand the ansi escape sequences. Either invoke rxvt through "rxvt -e
> >> bash --login -i" or change the default prompt to contain the actual
> >> control characters instead of the \033 bash-isms.
> >>
> >OK, thanks very much, just what I needed to know. Getting rxvt to run
> >bash explicitly works perfectly.
>
> FWIW, you can also set the SHELL environment variable to /bin/bash and
> rxvt will bring up bash automatically.
>
Even neater, thanks.
--
Chris Green (chris@areti.co.uk)
prev parent reply other threads:[~2004-01-03 19:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-03 12:27 Chris Green
2004-01-03 17:55 ` Igor Pechtchanski
2004-01-03 18:18 ` Chris Green
2004-01-03 19:00 ` Christopher Faylor
2004-01-03 19:19 ` Chris Green [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=20040103191921.GB8247@areti.co.uk \
--to=chris@areti.co.uk \
--cc=cygwin-xfree@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).