Randall R Schulz wrote:
It's no problem--I'll just stick with the previous "cygwin" termcap
entry. But why send a termcap entry and then wash your hands of the
consequences of it being used? You didn't include any disclaimers, so it
seemed like the courteous thing to do to let you know about th
Chuck,
At 15:52 2003-04-05, Charles Wilson wrote:
Randall R Schulz wrote:
Chuck,
I was meaning to write this up earlier, but work keeps getting in the way.
When I used your new termcap entry, "less" (when it's displaying
output piped to it via its standard input but not when it is given a file
na
Randall R Schulz wrote:
Chuck,
I was meaning to write this up earlier, but work keeps getting in the
way.
When I used your new termcap entry, "less" (when it's displaying
output piped to it via its standard input but not when it is given a
file name argument) tells me "WARNING: terminal is not ful
Chuck,
I was meaning to write this up earlier, but work keeps getting in the way.
When I used your new termcap entry, "less" (when it's displaying output piped to it
via its standard input but not when it is given a file name argument) tells me
"WARNING: terminal is not fully functional".
Here
Randall R Schulz wrote:
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
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" an
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 unc
On Wed, 2 Apr 2003, Randall R Schulz wrote:
> Charles,
>
> I must be missing something.
>
> At 00:29 2003-04-02, you wrote:
> >Charles Wilson wrote:
> >>Sorry, I haven't been following this thread. See below.
> >
> >>I'll try to figure out which parts are missing, and reinstate them --
> >>look f
Charles,
I must be missing something.
At 00:29 2003-04-02, you wrote:
Charles Wilson wrote:
Sorry, I haven't been following this thread. See below.
I'll try to figure out which parts are missing, and reinstate them --
look for a new release (of terminfo-) sometime in the next week.
Try the fol
On Wed, 2 Apr 2003, Charles Wilson wrote:
Charles Wilson wrote:
> Sorry, I haven't been following this thread. See below.
> I'll try to figure out which parts are missing, and reinstate them --
> look for a new release (of terminfo-) sometime in the next week.
Try the following. First, save /usr
Charles Wilson wrote:
Sorry, I haven't been following this thread. See below.
I'll try to figure out which parts are missing, and reinstate them --
look for a new release (of terminfo-) sometime in the next week.
Try the following. First, save /usr/share/terminfo/c/cygwin somewhere
handy. The
Chuck,
You're a scholar and a gentleman.
Thanks,
Larry
Original Message:
-
From: Charles Wilson [EMAIL PROTECTED]
Date: Tue, 25 Mar 2003 00:18:35 -0500
To: [EMAIL PROTECTED]
Subject: Re: vim quits and cygwin window contents not restored
Sorry, I haven't been foll
rses6 and also fails
to restore the window contents.
Randall Schulz
Larry
Original Message:
-
From: Randall R Schulz [EMAIL PROTECTED]
Date: Mon, 24 Mar 2003 20:14:55 -0800
To: [EMAIL PROTECTED]
Subject: Re: vim quits and cygwin window contents not restored
Larry,
At 19:38 2003-03-24
info 5.2-3 and doesn't work with 5.3-1. I'm using
vim 6.1.300-1 in a cmd.exe window running bash (2.05b-8).
Larry
Original Message:
-
From: Randall R Schulz [EMAIL PROTECTED]
Date: Mon, 24 Mar 2003 20:14:55 -0800
To: [EMAIL PROTECTED]
Subject: Re: vim quits and cygwi
Sorry, I haven't been following this thread. See below.
Randall wrote:
So, my bet is on the terminfo for cygwin as the locus of the problem,
whatever it is. Other reasonable hypotheses are that there's problem
in ncurses or in how Vim uses it.
Larry wrote:
Yeah, the terminfo change is the "prob
Larry,
At 19:38 2003-03-24, Larry Hall (RFK Partners, Inc.) wrote:
Randall R Schulz wrote:
Hi,
Some salient facts:
...
So, my bet is on the terminfo for cygwin as the locus of the problem,
whatever it is. Other reasonable hypotheses are that there's problem
in ncurses or in how Vim uses it.
Randall R Schulz wrote:
Hi,
Some salient facts:
Vim uses ncurses6:
% cygcheck vim
Found: D:\cygwin\bin\vim.exe
D:/cygwin/bin/vim.exe
D:\cygwin\bin\cygwin1.dll
D:\WINNT\System32\KERNEL32.dll
D:\WINNT\System32\ntdll.dll
D:\cygwin\bin\cygintl-2.dll
D:\cygwin\bin\cygiconv-2.dll
D
Hi,
Some salient facts:
Vim uses ncurses6:
% cygcheck vim
Found: D:\cygwin\bin\vim.exe
D:/cygwin/bin/vim.exe
D:\cygwin\bin\cygwin1.dll
D:\WINNT\System32\KERNEL32.dll
D:\WINNT\System32\ntdll.dll
D:\cygwin\bin\cygintl-2.dll
D:\cygwin\bin\cygiconv-2.dll
D:\cygwin\bin\cygncurses6
On Mon, 24 Mar 2003, Elfyn McBratney wrote:
> > It used to work for me, but a recent update has caused it to cease
> > working for me, too. Unfortunately, I'm not sure which--wasn't there an
> > ncurses update recently? Perhaps when it's convenient, I'll try to back
> > up to see if that makes scr
> It used to work for me, but a recent update has caused it to cease
> working for me, too. Unfortunately, I'm not sure which--wasn't there an
> ncurses update recently? Perhaps when it's convenient, I'll try to back
> up to see if that makes screen restore start working again.
>
> One other thing
-
From: Stephen Ehmann [EMAIL PROTECTED]
Date: Mon, 24 Mar 2003 13:57:02 -0800
To: [EMAIL PROTECTED]
Subject: vim quits and cygwin window contents not restored
Refer to:
http://sources.redhat.com/ml/cygwin/2001-03/msg01816.html
I still see that this is not working. Terminal contents are not resto
quits and cygwin window contents not restored
Works for me (tm).
Larry
Original Message:
-
From: Stephen Ehmann [EMAIL PROTECTED]
Date: Mon, 24 Mar 2003 13:57:02 -0800
To: [EMAIL PROTECTED]
Subject: vim quits and cygwin window contents not restored
Refer to:
http
Works for me (tm).
Larry
Original Message:
-
From: Stephen Ehmann [EMAIL PROTECTED]
Date: Mon, 24 Mar 2003 13:57:02 -0800
To: [EMAIL PROTECTED]
Subject: vim quits and cygwin window contents not restored
Refer to:
http://sources.redhat.com/ml/cygwin/2001-03/msg01816.html
I
Refer to:
http://sources.redhat.com/ml/cygwin/2001-03/msg01816.html
I still see that this is not working. Terminal contents are not restored.
Can I set anything to resolve this? Will the fix be in soon?
Thanks,
Stephen Ehmann
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-si
24 matches
Mail list logo
