in-window shell cannot parse history and incorrectly renders colors

[GoogleCodeExporter]

I'm not sure if this should be two Issue or one, but seeing as they are 
both related to problems with the in-window shell, I assume they are 
closely related.

-- Issue 1: Cannot parse history --
What steps will reproduce the problem?
Enter shell via ":sh"
Press Arrow keys or delete.

What is the expected output? What do you see instead?
I expect up and down to cycle commands, left and right should move the 
cursor, delete should remove the previous character.

Instead pressing up/down/left/right prints:
<9b>ku
<9b>kl
<9b>kr
<9b>kd
Once any of these keys have been pressed the shell no longer responds to 
ctrl+c or ctrl+d.  The window no longer responds to Cmd+w (I assume 
because all the menu keys are disabled while in shell mode).  The window 
does close if the Red X is hit though.

Pressing Delete replaces the previous character with "[K" but otherwise 
functions as expected.

-- Issue 2: Cannot Render Color Correctly --

What steps will reproduce the problem?
.bash_profile includes standard color settings:
  1 export TERM=xterm-color 
  2 export CLICOLOR=true

Enter shell via ":sh"
Enter command that renders in color (e.g. ls or grep --color)
Or...
Using a custom PS1 that includes a colorized prompt:
export PS1="\[\e[33m\]\$ "

What is the expected output? What do you see instead?
I expected to see colored text as output. (Even un-colored text would be 
acceptable)

Instead I see the color encodings of the text:
[34mDesktop[m[m      [34mLibrary[m[m    [34mPictures[m[m ...
-- Or --
[33m$

What version of the product are you using? On what operating system?

MacVim version: Version 7.1 (26)
MacOS X version: 10.5.2
Hardware: 15" Macbook Pro

Original issue reported on code.google.com by thezw...@gmail.com on 5 May 2008 at 12:33

[GoogleCodeExporter]

Shell support in GUI Vim is extremely limited.  On some platforms it works 
better than others, but this is a known 
limitation.  Unfortunately there is nothing that can be done in MacVim to fix 
this.  Search the vim_mac archives 
for more information.

Björn

Original comment by bjorn.winckler@gmail.com on 5 May 2008 at 1:34

[GoogleCodeExporter]

It turns out there is something that can be done about the problem where the 
editor window stops responding 
after having hit an arrow key.  I posted a patch for this on the vim_mac list a 
couple of days ago and the next 
snapshot will most likely include the fix for this.  (The other problems will 
still not be addressed though.)

Original comment by bjorn.winckler@gmail.com on 4 Jun 2008 at 7:42

[GoogleCodeExporter]

Snapshot 29 contains the fix I mentioned in comment 2.

Original comment by bjorn.winckler@gmail.com on 8 Jun 2008 at 1:55

[GoogleCodeExporter]

Original comment by bjorn.winckler@gmail.com on 13 Aug 2008 at 9:42

• Changed state: WontFix