This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: cygwin-1.5.6-1 Vim now broken

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 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 compared with such a problem.
> >
> >BTW, it's broken in everything (rxvt, XTerm, and cmd.exe).
> >
> >I guess it'd be a show stopper if screen were part of Cygwin.  Still, I
> >think it's more important than Vim, as there are a dozen editors but no
> >screen alternatives.
> That's truly amazing logic.
> 1) Vim is probably the most popular editor in cygwin.

And ? Would you care if it weren't part of Cygwin ?

> 2) It's a SEGV from cygwin.  It would be folly to ignore those.

Yes, and with 1.5.6 screen is so useless that a SEGV would be

> 3) As you note, screen doesn't even ship with cygwin.

Yes, but screen probably has more users than various packages
that ship with Cygwin. And it'd have many more if it were part
of it.

> >Anyway, I did what I could, reporting it before 1.5.6 -
> > .  I'm not
> >complaining.  I also reported it to the screen mailing-list today as
> >there are a few Cygwin users and one may be able to help you with it.
> "Help me with it".  Yeah.  That's one way to look at it.
> Why don't you help *us* with it by debugging the problem?  I don't
> really care about screen but if it's important to you then some
> hours with gdb might be in order.  That's what I do with problems
> that I care about.

Do you think all users are Cygwin developers and know how to
debug such things ? I couldn't even debug the ELinks problem I
had, where none of the commands (bt, info threads, thread 1...)
that work on Linux showed anything useful. Now you suggest I
spend some hours with gdb. Doing what ?

I guess it's easier to go through the snapshots from the first
2 months after 1.5.5. Are they available somewhere or tagged in

How to contact me -

Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]