On Tue, Jan 20, 2004 at 09:59:21AM -0800, Rafael Kitover wrote:
>You will not be able to use gdb on a screen binary directly, as you
>will get a "must be connected to terminal" error, use something like:
This isn't necessary. You should be able to:
c:\>set CYGWIN=notty
c:\>gdb screen.exe
(gdb) s
On Tue, 20 Jan 2004, Frédéric L. W. Meunier wrote:
> On Tue, 20 Jan 2004, Christopher Faylor wrote:
>
> > On Tue, Jan 20, 2004 at 03:47:39AM -0200, Fr?d?ric L. W. Meunier wrote:
> > >[snip]
> > >I guess it'd be a show stopper if screen were part of Cygwin. Still, I
> > >think it's more important
>-Original Message-
>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christopher Faylor
>Sent: Tuesday, January 20, 2004 9:11 AM
>To: [EMAIL PROTECTED]
>Subject: Re: cygwin-1.5.6-1 Vim now broken
>
[SNIP]
>>I guess it'd be a show stopper if scree
On Tue, 20 Jan 2004, Christopher Faylor wrote:
> On Tue, Jan 20, 2004 at 03:47:39AM -0200, Fr?d?ric L. W. Meunier wrote:
> >On Mon, 19 Jan 2004, Christopher Faylor wrote:
> >>And, no, screen becoming screwed up in an rxvt session is not a show
> >>stopper.
> >
> >Yes, but it's something that will
On Tue, Jan 20, 2004 at 03:47:39AM -0200, Fr?d?ric L. W. Meunier wrote:
>On Mon, 19 Jan 2004, Christopher Faylor wrote:
>>And, no, screen becoming screwed up in an rxvt session is not a show
>>stopper.
>
>Yes, but it's something that will make all screen users not upgrade to
>1.5.6 or downgrade to
Corinna Vinschen wrote:
On Jan 20 07:11, David Rothenberger wrote:
Christopher Faylor wrote:
Editing files works fine, AFAICT. Vim seems to be dying on exit.
I don't know if this will help with this problem, but I had the same issue
under Windows XP Pro. The problem occurred with files on whi
On Jan 20 07:11, David Rothenberger wrote:
> Christopher Faylor wrote:
> >Editing files works fine, AFAICT. Vim seems to be dying on exit.
>
> I don't know if this will help with this problem, but I had the same issue
> under Windows XP Pro. The problem occurred with files on which SYSTEM was
Christopher Faylor wrote:
On Mon, Jan 19, 2004 at 09:39:19PM -0500, [EMAIL PROTECTED] wrote:
I installed the new 1.5.6-1 and rebooted. I then went to edit a file with
vim. I changed one line of code and went to save the file. This is what
happened:
- vi FA_lib.pm
'Vim: Caught deadly signal SEGV
Vi
* Frédéric L. W. Meunier (2004-01-20 06:47 +0100)
> On Mon, 19 Jan 2004, Christopher Faylor wrote:
>> And, no, screen becoming screwed up in an rxvt session is not
>> a show stopper.
>
> Yes, but it's something that will make all screen users not
> upgrade to 1.5.6 or downgrade to 1.5.5 when they
On Mon, 19 Jan 2004, Christopher Faylor wrote:
> And, no, screen becoming screwed up in an rxvt session is not
> a show stopper.
Yes, but it's something that will make all screen users not
upgrade to 1.5.6 or downgrade to 1.5.5 when they see how broken
it's. Broken dettach / reattach is nothing c
>-Original Message-
>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christopher Faylor
>Sent: Monday, January 19, 2004 8:37 PM
>To: [EMAIL PROTECTED]
>Subject: Re: cygwin-1.5.6-1 Vim now broken
>
>And, no, screen becoming screwed up in an rxvt session i
On Mon, Jan 19, 2004 at 09:39:19PM -0500, [EMAIL PROTECTED] wrote:
>I installed the new 1.5.6-1 and rebooted. I then went to edit a file with
>vim. I changed one line of code and went to save the file. This is what
>happened:
>
> - vi FA_lib.pm
>'Vim: Caught deadly signal SEGV
>Vim: preserving file
I installed the new 1.5.6-1 and rebooted. I then went to edit a file with
vim. I changed one line of code and went to save the file. This is what
happened:
- vi FA_lib.pm
'Vim: Caught deadly signal SEGV
Vim: preserving files...
Basically I cannot use Vim to edit files - as it now stands.
Used
13 matches
Mail list logo
