Re: vim quits and cygwin window contents not restored

[Randall R Schulz <rrschulz at cris dot com>]

Hi, Chuck,

Thanks for the clarification. I have no idea what was up with the MIME 
encoding or whatever it was that glitched.


At 20:16 2003-04-02, you wrote:
> Randall R Schulz wrote:
>
> > Since there were no attachments, I placed the text embedded in the 
> > message into a file named "cygwin.terminfo" and used "tic" as you 
> > prescribed. I get a diagnostic "Name collision between cygwin 
> > cygwin". I tried removing the existing terminfo entry, but the result 
> > is unchanged.
>
> Igor is correct.  There were two attachments, but the web archive 
> inlined them.  If you go to gmane, you'll see the attachments in their 
> original form.
>
> But that shouldn't matter too much.  The first attachment (or part) is 
> the terminfo input -- the commentblock all the way down to the last 
> "dense" block of 20 or so lines.  That "dense" block is the termcap 
> entry.  You don't want to 'tic' that; it was generated from the longer 
> file using 'tic -C' -- but any codes that termcap doesn't understand 
> are dropped.  So converting it BACK to terminfo format is a lossy conversion.

Thanks for the clarification. I've set things straight with the 
terminfo entry. Vim seemed to work perfectly well with the termcap 
entry for some reason. The tabs all made it through intact.


> Again, you want the first group.  But, if you're cut-n-pasting, you 
> need to insure that each line begins with a tab, not 8 spaces 
> (sometimes tic can be picky about that).
>
> > > You can also hand edit /etc/termcap (back it up, first) and paste 
> > > the attached cygwin.termcap file into it, deleting the current definition.

Can I trouble you to explain why your termcap replaces something so 
different in the existing /etc/termcap file:

cygwin:\
    :xn@:op=\E[39;49m:Km=\E[M:te=\E[2J\E[?47l\E8:ti=\E7\E[?47h:tc=linux:

I understand that this entry incrementally modifies the "linux" entry. 
Your new one does not? You just decided to sever the connection? 
There's too much difference to handle this way? It was a bad idea for 
some reason?

Enquiring minds want to know. Dammit.

Just to avoid bridge burning, I added your new entry and renamed the 
old cygwin one.


> ....
>
> --chuck


Thanks for fixing this up. It was a little annoying not to have the 
screen restored.

Randy 


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/